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.
Julie Edwards
about 6 years ago
in To-dos
3
Unlikely to implement
Create multiple features from a single work request
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.
Connie Lin
about 3 years ago
in To-dos
0
Future consideration
When filtering by Todo status, I also need to see Features that do *not* have a todo
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...
Florian Cheval
over 6 years ago
in To-dos
0
Unlikely to implement
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 ...
Guest
almost 10 years ago
in To-dos
2
Already exists
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...
Ray Devenney
over 3 years ago
in To-dos
0
Future consideration
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...
Guest
about 7 years ago
in To-dos
0
Unlikely to implement
My team would use this functionality so that reviewers (who don't do that much work in Aha and aren't that used to the tool) can go in and either complete a to do or accept/reject an approval and by doing that trigger a rule, so that the status ca...
Fredrik Örn
over 3 years ago
in To-dos
0
Future consideration
Allow ability to mark a "To-Do" as "Unassigned" instead of defaulting to the user who wrote the Feature Card
As the Project Mgr for my Dev team, I oftentimes am the one driving the planning sessions and writing the Feature cards. Currently, any To-Dos written on a Feature Card are assigned to me automatically since I'm the one writing the card/to-do. I w...
Danette Colin
over 7 years ago
in To-dos
2
Already exists