All ideas
Sort by:
Trending
Status:
Showing 8935
2
VOTE
Status pills should use the defined color
What is the challenge? Although colors have been defined for a status, the color changes and shows as lighter when in views where the element appears as a pill. What is the impact? Only a cosmetic impact, and doesn't affect other use of Aha! Impac...
2
Future consideration
3
VOTE
Have release phase custom fields be a part of release templates
Who would benefit? Many teams use release templates to make it easy to build complex release plans and reuse them with every release. Now that we can add custom fields on release phases, these teams are using these to manage the complexity of thei...
1
Future consideration
17
VOTE
16
VOTE
View in Aha! the author of a comment created in Azure DevOps
In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
1
Future consideration
44
VOTE
Update Feature ID when moved to another product
When you create or copy a feature, its ID is automatically created based on the product code. The ID is a combination of the product code and an auto number (and that is perfectly fine). But when you change the release reference to a release of an...
10
Future consideration
11
VOTE
Add unique identifier to organization drop-downs
We have duplicate org names, that are only unique thru their client id. We need the ability to be able to determine the correct org (e.g. for adding an idea), by adding the client id to the organization dropdowns (e.g. Boeing 12345)
0
Future consideration
13
VOTE
Option to include a set of watchers on new releases
Currently, watchers are not copied when copying a record and there isn't an option to add watchers in the release template settings. It would be helpful to have the option to copy a release from the parking lot with the set of watchers, or include...
1
Future consideration
11
VOTE
Jira integration user name
In both Jira and Aha!, you need to have a user that has the appropriate permissions which is often a highly privileged user. However, when setting up the integration, there is no way to indicate an alias name to use for the integration. Consequent...
0
Future consideration
9
VOTE
Automation Rule - Add "Release" as an Action
In my scenario, there are times that a feature is in a given status, and as a result, I would want that feature to move to a different release. For example, If I abandon a feature, I want it removed from a release and put into a parking lot where ...
1
Future consideration
16
VOTE
Include Milestones in the expanded Release names section of the Epics Gantt Chart
Many companies use milestones to represent when a set of work items is to be delivered and these are only loosely coupled or decoupled from longer-term planning time boxes, which in Aha are best represented by Releases (e.g. quarterly time boxes)....
2
Future consideration