To-dos

My team uses to-dos to track non-development/engineering tasks that need to completed. We'd love to filter to-dos in a list report by the associated record, so we can look at the to-dos specifically on initiatives, releases, epics, etc. to match t...

What is the challenge? Users would like to see their to-dos grouped by parent epics and child features all together. Current, in the roadmap view, features won't nest under their parent epics. What is the impact? It is very difficult to see all th...

What is the challenge? Currently when a work request is created and aligned to a workspace and it's relevant feature is updated the work request in other workspace is not updated auto. What is the impact? User has to manually update the descriptio...

Right now, if a to-do is checked off, the user has to go into the to-do itself and uncheck it from the box in there. It would be great if you can uncheck it from the main check box.

Hello. I'd like to be able to put more than one approver on an approval task and have either approval mark that to-do as complete. Right now it is structured as an AND function rather than an OR. (ie. Assignee 1 AND Assignee 2 must approve. I want...

For people that do not track to-dos by date but by priority instead

What is the challenge? Conceptually, a to-do on a feature having a record link is no different from a requirement on a feature having a record link. The to-do could be blocked by or block any other record, it could depend on or be depended on. Sev...

While creating dependency on another workspace, the aha record needs to be tagged at requirement level. It would be great to see that option considering the high usage of work request related to requirements.

If I have complete a to-do, my “PERSON assigned you a to-do” notification should be marked as read if it is not already.Right now, I work through my to-dos then come to notifications and have to go through them all again and mark as read.

We are using work requests to share requirements across workspaces. Since users who will receive work requests must have at least View rights to the sending workspace, it would be useful to know who will receive the request to make sure their righ...