Application
Sort by:
Popular
Status:
Showing 7152
2
VOTE
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
0
Future consideration
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
Future consideration
2
VOTE
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
Future consideration
2
VOTE
2
VOTE
2
VOTE
Apply estimates as completed work for features imported as "shipped"
Currently you can set capacity so that remaining estimates are applied as completed work when a feature is set as shipped. However, when importing from JIRA (or CSV) an imported feature to an active release that is marked as shipped does not apply...
0
Unlikely to implement
2
VOTE
