All ideas
Sort by:
Trending
Status:
Showing 8941
2
VOTE
Ability to add context to to-do e-mail reminders - for ex: Initiative Name - to-do; Release Name - to-do
Aha! sends out the "consolidated" to-do notifications in e-mails which is a nice functionality. However, as the number of to-dos increase from various goals, initiatives, releases the confusion increases as to which context these are related to. F...
3
Already exists
2
VOTE
Ability to add specific field from elements like feature (currently only defaults to feature name for example)
When adding other entities like scenarios to a feature, it is useful if we can associate a feature number rather than the feature name which is the default field when you use the many to many table
1
Already exists
2
VOTE
Don't change case of customized terms in Terminology
As a Product Manager, I want terms to be displayed a certain way so that it communicates my intent. Instead of "feature", I prefer the "PBI" and "Product Backlog Item". My terms, however, get as "Pbi" and "Product backlog item", respectively. I th...
1
Already exists
2
VOTE
JIRA and Aha synchronized numbering
We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...
0
Unlikely to implement
2
VOTE
2
VOTE
1
VOTE
Show workspace name with release name for notifications
Overview When receiving a notification that someone moved a feature to a new release, I can't see what workspace it was moved to. Challenge The release name by itself is not enough to provide all of the information/context. Desired user experience...
0
Future consideration
2
VOTE
Automatically include links in dependency vizualization
I love the visual dependency map. One enhancement I would like to see considered is that initiatives that have other initiatives roll up into them should show automatically in the dependency map even though an explicit "link" has not been establis...
0
Unlikely to implement
2
VOTE
2
VOTE
