Skip to Main Content

Share your product feedback

ADD A NEW IDEA

My ideas: To-dos

Showing 194

Allow external team members to Approve work via To-dos

What is the challenge? We need to get some sort of Approval or Sign-off from our customers (not Aha! users under our account) on the requirement or feature that we have created for them. What is the impact? We need our external customers to agree ...
Guest 8 months ago in To-dos 0 Future consideration

Hide workflow approval groups on to-do when no workspace users assigned

What is the challenge? All account approval groups populate for the approval group field on approval to-dos, even when no users from a given workspace are assigned to a group. This creates a challenge for someone to select the correct approval gro...
Jeanette Resnikoff 8 months ago in To-dos 1 Future consideration

Allow to-do's to be moved to iteration records

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...
Brittany Rhoney 9 months ago in To-dos 0 Future consideration

When accepting a work request, allow fields with same API_key to carry over from requesting record to new record

Who would benefit? Product Owners and Cross Functional Teams What impact would it make? Eliminate having to copy information from 'depends on' records into 'dependency of' records How should it work? It would work like it does when promoting ideas...
Guest 9 months ago in To-dos 0 Future consideration

Ability to associate ToDo items to workspace (not the Initiative/Epic/Feature)

Who would benefit? Product Managers and PM Leaders What impact would it make? Allow us to get more value out of Aha! by using Aha! ToDos for regular activities required of a team How should it work? Allow a ToDo record to be created as a child of ...
Guest 9 months ago in To-dos 0 Future consideration

Import Approvals via CSV

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,...
Guest 10 months ago in To-dos 0 Future consideration

Allow setting approvals to "any" or "all" when configuring automation rules to trigger approvals

Who would benefit? Users who require all members of an approval group to grant an approval What impact would it make? Right now it only allows "any" member which allows approvals in this scenario to proceed prematurely How should it work? Much lik...
Stephanie Lechner 10 months ago in To-dos 1 Future consideration

Automation rule to trigger a To-Do based on “Complete by date” custom field

Who would benefit? Management What impact would it make? Timeliness completion of releases How should it work? The rule would trigger a To-do for the owner on the date shown in the 'Complete by date' custom field rather than the fixed amount of da...
Guest 10 months ago in To-dos 0 Future consideration

Allow me to create a batch of individual to-dos or work requests

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...
Reilly O'Connor 11 months ago in To-dos 0 Future consideration

Add Todo item ~ close (x) broken

Who would benefit? All users (on iPads?) What impact would it make? Improve usability, fix broken functionality How should it work? X in upper right of modal should close/cancel Add user flow.In fact, better yet, fix that and add a Cancel button
Richard Price 11 months ago in To-dos 4 Unlikely to implement