All ideas
Sort by:
Trending
Status:
Shipped
Showing 2525
21
VOTE
Automatically add description from work request when accepting and promoting
When I create a work request, I add the details to the description field, and when it's accepted and promoted to an issue type, I would like to see the two description fields mapped so the content is easily accessible on a single screen that can t...
1
Shipped
68
VOTE
Enhance two-way sync with Rally to support Rally -> Aha!
Features are created in Aha! and then pushed to Rally. User Stories (US) are created in Rally and associated to the Features. These associated User Stories should be synced back to Aha! and associated with their respective Features as Requirements
15
Shipped
52
VOTE
Allow custom statuses to inherit from product line
The update to allow customizing the default status is great.
However, it doesn't solve the problem where we have multiple business units in a single account and each business unit has their own distinct workflow for their portfolio of products.
Se...
8
Shipped
7
VOTE
Edit the documents in a KB outside of the existing parent line
What is the challenge? Currently when you create a knowledge base , you select the root document to publish. Any child notes nested underneath it are included as well. There is a need to edit the documents in a KB in a broader way. How would you s...
0
Shipped
65
VOTE
40
VOTE
JIRA Epic % complete to Feature Progress
The Feature Progress field is a very effective visual of Feature % done, but there is no option to map the Progress from the JIRA Epic record using the Epic % complete value which is derived from the number of completed stories for the Epic.
Our I...
11
Shipped
60
VOTE
66
VOTE
Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature
The specific use case that this commonly occurs for is the following mapping:
Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well.
Current behavior: The int...
13
Shipped
43
VOTE
Create a 'clean' release template from an existing release - that other products can also use
Have the ability to create a clean (non populated) release template from a current release. And that this new release template is then visible in the drop down list in the 'release phase template' section when creating a new release. This would th...
3
Shipped
53
VOTE
Allow to define a default release for new Features
We create a lot of features via the New Feature dialog. All these features are assigned to the Parking Lot release. Aha uses the first real release in the list as selected default entry.
It would be much better, if we could configure, which releas...
11
Shipped
© 2025 Aha! Labs Inc.•All rights reserved