Similar to Capacity line in the feature board , we would like a target, commit, and stretch line with user defined % of capacity. Ex, 80% = commit, 100% = Target, 120% = Stretch with 3 lines. This way I could have a quick visual of my capacity in ...

We attach a lot of ideas and/or features to epics, initiatives, and goals. That level of granularity is not needed in the presentation itself or the initial webpage view, in which we display only high level planning objects (initiatives, epics, go...

What is the challenge? Users capture important details about an epic or feature in the description of the record, which is a note-type field. In some cases, the user needs to mention another record and does so using the "#" mention. Today, the men...

We have a central point of contact for users to get in touch with us. It is via JIRA Service Desk. To keep it central, but efficient, it will be good if a submission into JIRA Service desk can take a particular issue type and automatically submit ...

What is the challenge? Business Problem to Solve: Utilization report: We would like to know who is utilizing the Aha Account Level? How can we manage the amount of changes made by a user when Account Level permissions have been granted? License co...

What is the challenge? Inconsistent dropdown styles can confuse users and lead to usability issues. What is the impact? Improves user experience by providing a consistent interface, making Roadmaps easier to navigate and use Describe your idea Sta...

If a feature or requirement has an estimate of 5 days, then the corresponding estimate will count as 40 hours in the pivot table (for example when the requirement's estimated effort is summed as the cell value). This can result in figures that are...

What is the challenge? There are a few ways records can be created today: Via the UI Copied Converted Via an integration It is not easy to quickly understand the source of record creation. What is the impact? Teams are trying to understand where r...

What is the challenge? There is no visibility in Aha! what issue type the Requirement is in Aha!. In addition, we'd like to create Design tasks in Aha! which don't require sync to Jira, whereas we'd like to sync Backlog Items, Activities, and Bugs...

What is the challenge? Too many clicks to find and select desired agent and prompts. Getting pushback on end-users adopting workspace agents & prompts we've built What is the impact? hampers adoption and increases chances users miss a ...