To-dos

In addition to the existing statuses (Pending, Overdue, Complete), I would like a new status called Not Required. Currently we annotate the To Do title with n/a - however it would be easier to have this as a status as this would aid with reporting.

I use filters a lot for too many activities to describe here. One of them is to verify that once "All the todos have been completed", a Feature should be in a "Ready to develop" status. I also use the Todo status filter everyday to discuss progres...

Would save me from navigating to All work view to add a to-do.

When creating a task for a feature, everybody can read it. However, some tasks are only from e.g. a manager to a specific employee. In such a situation, only the manager (aka the creator of the task) and the employee (the assigned) should be able ...

Often times a work request may encompass the work that needs to be split out into multiple features and we would like to be able to create multiple features before a work request is completed.

Would like to be able to add tasks to releases. Often we have tasks that are associated with the release as a whole and no good place to put them.

When creating an automated to do, it could be possible you want it assigned to multiple people. You can do this if you have the specific users. Although when you select same as, you can only pick one 'same as'. It would be great if we could have s...

Need ability to filter tasks by status and/or the owner of the task. Currently this type of filtering is only applicable to Get All features API but not the task API.

When I get a todo email it tells me the release name but not the product. Is there a way of including which product this refers to in the todo emails? As in “Product name” then > release phase > release name > ….. Or even in the todo page...

Provide more precise control of timelines by linking To-Do due dates to their associated Feature's due dates.