Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Delivery

Showing 174 of 9642

Add AI to the develop side in order to analyze backlogs, sprints, features etc.

What is the challenge? Would like to use AI to help find inconsistencies with backlog items, or analyze the efficiencies/inefficiencies of sprints What is the impact? AI has been added in several places in Aha! but not over in Develop. Describe yo...
Jennifer Lange 7 months ago in Delivery 3 Future consideration

Aha! Develop - Reopen a completed sprint

It is possible to re-open a shipped release to make changes that should have been included. The same logic should apply to sprints as there are various reasons I may need to make changes.
Dale Potter over 3 years ago in Sprints 2 Future consideration

Filter using Feature location in Aha! Develop

What is the challenge? Currently, you cannot filter records within Aha! Develop screens, like the parking lot by the feature location field (backlog management, sprint, workflow board etc.) What is the impact? This would allow teams to filter the ...
Chris Quigley 7 months ago in Delivery 0 Unlikely to implement

Count the number of times a feature or requirement goes into a status

What is the challenge? For development cycles (Aha Develop), it's important to know how many times a feature is returned to development as a means to determine if a developer is doing proper unit testing or adhering to acceptance criteria. W...
Guest 4 months ago in Delivery 0 Future consideration

Mermaid text generated diagrams

Allows much easier to iterate, more standard, and simpler to follow along version of diagrams/charts within documentation. GitHub and Notion have recently adopted the same library (mermaid) allowing for standardization across tooling.
Barnett Klane over 3 years ago in Delivery 0 Future consideration

Enable automations to work with custom "One to Many Relationship" tables

It would be great if we can have automation rules working with "One to Many" relationship type of custom tables. We use a custom table to track risks in issues in multiple record type and would be great to add new records based on a trigger at the...
Edgar Holguin about 2 years ago in Workflow boards 0 Future consideration

Allow exit criteria for each status in a workflow board to help users understand when they should progress an item to the next status.

What is the challenge? this information is currently stored outside of the tool making it unlikely for users to follow company guidance What is the impact? teams are progressing items that are not ready. we are building exceptions reports to fulfi...
Guest 9 months ago in Workflow boards 1 Future consideration

Restrict ability to open or close sprints

What is the challenge? On some teams, only certain team members are allowed to start or close a sprint. Currently anyone with contributor access can open or close a sprint. What is the impact? Sprints are open or closed in error. Describe your ide...
Emily Yankush about 1 year ago in Sprints 1 Future consideration

Automation: require field based custom field option

What is the challenge? During the lifecycle of an Epic, we have fields that when a certain option is selected, another field should be required. What is the impact? Data is not complete so reporting is incorrect. We have features that that when a ...
Diane Metzger 4 months ago in Delivery 0 Future consideration

Consistency between Roadmaps and Develop for record workflow

For the following Record Types (Epic, Feature, Requirement) In roadmap we can set each record type with its own workflow. However in Develop you can only pick one workflow for all three record types. We would like to have a consistent process of h...
DataGuy over 3 years ago in Backlogs / Workflow boards 0 Future consideration