deontologician/cyclence

The recurring task tracker

cyclence's Issues

Nice 404s

The 404s are default very ugly and bad currently. Switching to a javascript frontend should mitigate this, but they still can't just be text on a white background.

security

Is this task list private? If so, are there settings and sharing options?

Add ability to "skip" a task instead of completing it

Sometimes tasks aren't "completed" but they don't need to be done this time (or someone else did them)
Differences from completions:

• show as "skipped" rather than "completed"
• no points awarded

All mapped objects should have a __str__ and __repr__ representation

This is a cleanup piece

Convert from glyphicons to font awesome

This will allow coloring icons (red notifications etc)

Automate deploy

Currently deploying Cyclence is a multi-step process which is quite ugly.

• Automate deploys with fabric

Add AGPLv3 files to repository

Currently, there is no licensing information. The intention is for it to be licensed AGPLv3

Make a clear separation between "due" and "not due" tasks

Probably need to add a dividing line between due and not_due

"about" page

Add an informational page about the software and what users can expect to do with it. Can it accept imports (or be exported)? Be viewed elsewhere? And give yourself some publicity.

Add massive point scoreboard at top right

Points are kind of hard to get excited about at the moment

Sort completed and "not due" tasks to the bottom

Currently, a task that is not due or already completed today may not appear at the bottom.

Sessions should be created per request, not per application

Currently, sessions are created per application, and hence not flushed/refreshed for every incoming request, leading to stale data in some tornado processes.

Group tasks by tag in the task page

Currently, you cannot organize tasks by tag. This should change.

Add ability to deactivate a task

This would prevent it from being due, but keep the record of the task and its completions (and allow reactivation later)

Pull Hue out of the task class

The hue method on Task is not the right place to have display logic.

• It should be a function that is somewhere closer to the template rendering logic
• It should be based on the points the task is worth today, and whether it can be completed early

Generalized notification to send to all users of a task

Currently, notifications are on a per-user basis. Add some convenience functions that allows a notification to be sent to all users on a task.

Sorting of tasks should take into account range of point values a given user has

Currently, sorting does not account for the range of points a user actually uses on his tasks. The application should function just as well if someone uses [1-5] point scale verses a [1k-10k] scale

"due" field

It would be nice to have a calendar option for the "due" field.

Add an introduction page to the logged out version of the site

Currently, cyclence is a bit non-descriptive in terms of why you should "log in".

Bootstrap has the hero-unit which should be decent for adding a description to logged out cyclence

Add ability to share a task when it is created

Currently, you must create the task, then view it and then share it. Ideally, you could share it immediately upon creation.

User interface suggestion: Move "Edit Task" to the task's modal dialog.

The delete button is already there and it would avoid having two places where the user has to pick a task from a list.

If a task has no tags, it has an empty string tag

Instead, it should have: actually no tags.

Add ability to edit a task

Tasks currently cannot be edited, just created, deleted, shared and completed.

Using the "Invite" button results in a HTTP Error 500

Using the "Invite" button results in a HTTP Error 500 after entering somebody's e-mail. It doesn't really say much else.

If a task can be completed early its points should increase until the due date

Basically, right now the graph of point worth is like this, as a task nears and then passes its due date:

------
      \
       \
        \

It should be like:

   _
  / \
 /   \
/     \

This will make issue #1 duplicate less logic from the point_worth method, since it will work the same (rising and then falling)

Add ability to complete tasks on behalf of other people

Task list has to be manually refreshed.

The task list doesn't automatically update, so if the browser is left open, things look like they aren't due until it's manually refreshed.

Add a datepicker to the date field

Currently, you have to type the date into a field with no validation. This is bad.

Sharing should have edit/view/complete permission groups

Currently sharing is all or nothing. The user->task mapping should have a permission type on it (and perhaps later permission groups could be created, we'll see)

Add randomized tasks

Add the ability to make tasks that have fuzzy recurrence dates.

So, for instance "recur about every 3 months". And it will pick a random date to turn green on. Each time it is completed, it will pick the next date randomly

Convert from serverside templates to backbone.js

This is a large change, but one that will pay dividends in responsiveness and flexibility

Add user handles

Currently, the application uses the email address as a unique identifier, but this is probably not optimal in the long run (for spam etc). So, add an interception page after first authentication that allows them to pick a Cyclence specific handle (defaulting to the email portion before the @)

Allow customizing completion

Currently, the only completion action that can be taken is "I completed this today". It should be possible to say "I completed this two days ago", and add a comment to the completion

Add link from logged in cyclence to issue tracker

If there is a bug, it should be easy to report it