To-dos

What is the challenge? Currently, it's not possible to bulk edit custom fields on Approvals What is the impact? Time consuming to update custom fields across multiple approvals or to-dos. They either have to be done manually, or via a CSV update,...

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

What is the challenge? You cannot generate a report of upcoming to-dos that filters out multi-assignee items you’ve already completed. These to-dos continue to appear in your list because the overall status stays “Pending” until all assignees fi...

Who would benefit? Project managers and organizations are looking to have better project management capabilities in Aha. What impact would it make? It would allow us to automatically adjust schedules when we have dependencies built in and a task t...

Who would benefit? Teams with large deployments who make heavy use of to-dos and work requests to track cross-functional work What impact would it make? Today, if I need to assign a to-do or work request to a large number of recipients, I have two...

What is the challenge? Completed to‑dos in Aha! are always shown with a fixed strikethrough style, and users have no control over this visual formatting. When product managers or team members need to present or document completed tasks—such as i...

What is the challenge? Aha! cannot currently auto-copy the description from a work request into the description of the feature created from it. When you accept a work request and add a record, only the name and link/relationship are created; the...

What is the challenge? Today, when reporting on To-Dos, you need to pull in three different objects to get To-Dos, Approvals & Work Requests in a report view. This will put all three of these items on the same line in list views and pivot view...

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

I think todos have a lot of potential to represent non-feature work across Aha. I like the idea of not "polluting" aha with workarounds where features are used to represent work, nor requirements used to represent non-feature related work. There i...