To-dos

We use To-Dos extensively to track activities and store documents within our Phases. However, once a To-Do is completed the crossed out title makes it difficult to read and find the To-Do we are looking for. Having completed To-Do items checked of...

What is the challenge? When creating to-dos within a release template, only Title, Description, and Assigned To fields can be configured. Custom fields cannot be set in the template, requiring manual updates to custom field values every time a r...

It would be great if the Kanban board could be used with other record types, such as to-dos, mainly because to-dos can be used across multiple levels of the product hierarchy. Need a workflow for PM and UX teams that relate to todos. What ...

What is the challenge? I sometimes get assigned to-dos that are time consuming tasks that may take a few hours of time to finish spread over a few days. Currently, I have no way to indicate that I have begun work on the to-do other than adding a m...

What is the challenge? managing change requests What is the impact? simplify approvals for specific task types Describe your idea looking to be add template approval types to support various use cases and pull a standard set of information from us...

Who would benefit? Develop users What impact would it make? Currently users are able to move to-do records to all other roadmap record types (goals, releases, epics, features, etc), but not iterations. Iterations already support to-do's so this wo...

Who would benefit? admins who need to create structured approvals, anyone who needs to create many approvals What impact would it make? save time and align functionality of the tool How should it work? in the same way that to-do's can be uploaded,...

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...

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.

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...