RELATED IDEAS
Allow To-do's to be moved
I often create to do's while on calls and sometimes its not always clear / easy to assign them to an epic right away. Or, the to-do is to find out if the to-do should really be a to-do ;-) and once confirmed it is, needs moved to a epic.
| Release time frame | 3 months |
-
ADMIN RESPONSEAug 4, 2023
It is now possible to move to-dos. You can find this option in the
...menu.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
1
MERGED
9
MERGED
15
MERGED
Ability to assign/reassign a to do to a product/feature/release
Merged
When you create a to do from the 'mywork' page, sometimes the to do does not get attached to the product currently active. At the moment we can't link the to do to a product, feature or release later on. I personally created a report (list) to see...
0
Shipped
9
MERGED
Ability to "reassign" a to-do to another phase/parent
Merged
To-dos should be able to be moved. Either assign it to a new phase or release or for those that are "orphaned" be able to put them under a parent. To-do's can capture a lot of attachments, conversations, etc that should be moved when the to-do has...
0
Shipped
8
MERGED
8
MERGED
8
MERGED
8
MERGED
Ability to reassign "orphan" todos
Merged
I notice that I can create a todo with no relation to anything in Aha - product, release, etc. That's a very useful feature to quickly capture something that needs to be done, say on the app. However, it would be useful to assign these todos aroun...
0
Shipped
3
MERGED
1
MERGED
2
MERGED
2
MERGED
Allow user to designate what a 'to-do' is Related to
Merged
As a product manager or user of Aha, we would like the ability to modify or configure what a 'To-Do' is Related to. For example, if an existing 'to-do' should be moved to a different feature, we would like to change what it is related to. We do no...
1
Shipped
Love it! Bravo!
Excellent update! Thank you!!
This missing functionality presents a challenge. I am Scrum Master for two teams. I create User Story Templates with multiple default To Do's. It would be ideal if I could simple copy the multiple To Do's without having to manual cut and paste each one individually.
I have the same challenge. I have created a to-do by using the slack integration but I am not able to link it to a record (in this case it is an epic but could be anything else). So basically if the to-dos is not assigned to me I can easily get track of it. It would be really helpful if we could able to link the to-do to a record and also move an existing to-do to another record instead of having to create it again.
Posted the wrong link: https://big.ideas.aha.io/ideas/A-I-11486
I just created a new Idea and then found this one. I think it is the same. We would really appreciate the consideration or options for a workaround. https://big.ideas.aha.io/ideas/APP-I-5830
I recently created custom to-dos complete with hyperlinks to appropriate information. I created them in 3 separate feature cards. They I found 3 todos where in the wrong feature card. I agree it would be nice to select a new destination to attach this todo to. It does not happen a lot, but it's a nice to have
Same here, many times I create to-do's while on call using the slack integration, and would like to later move them to their respective features/epics etc
This would be incredibly helpful as we create a task in one activity when we're brainstorming that may end up needing to be put into the actual projects once it's approved. Just like we can copy a project or activity over, to-do's would be the icing on the cake :)
I really really really would love this. Sometimes we realize that we have to break something apart or an improvement needs to be split away from a feature that we want to ship part of. I have to manually move To Dos and it's labor intensive. Team mates who are hesitant about the utility of To Dos feel justified in not using To Dos within Aha! because they feel permanent.
I just shipped a release with a feature that had 20 to-do items. But 5 of them we deferred and didn't include in the shipped feature. This use case is really frustrating. I ended up copying the feature, then deleting all the incomplete to-do items from the feature to ship, and deleting all the incomplete ones from the copy. This took about 5 minutes.
For me, a workaround to the ability to move to-dos would be to have an option when you copy a feature to exclude completed to do items. That would at least get me 80% of the way there if the ability to move to do items is structurally difficult/large project for Aha.