Dependancy Map using already existing relationships
We have an Epic (Initiative) - Feature - Requirement breakdown structure. It would be very useful to be able to visualize the dependencies using these existing relations instead of requiring to add separate link specifically for the dependancy map.
Kenneth Palm
about 9 years ago
in Features
1
Will not implement
Customize the Requirements View under Feature Custom Layout
I would like to be able to add the Story Point estimate so that you can see at a glance how large each story is without having to click on the story to open it up. (see screenshot)
Nate Hicks
almost 5 years ago
in Features
1
Future consideration
When using requirements for estimations as an input to roadmap planning, it would be helpful to be able to add a standard set of requirements to the feature, for example where each requirement might identify a different resource type for estimatio...
Guest
almost 10 years ago
in Features
3
Already exists
What is the challenge? Every time we add/modify a score for a feature we have to manually have Aha sort by score (or any other measure). What is the impact? It's not a significant impact, but its not effective to have to manually click the sort fe...
Justin B
10 months ago
in Features
0
Future consideration
What is the challenge? When linking a feature to an epic you cant limit the epics you can view What is the impact? Limiting the amount of epics you can view will make it more self explanatory, for big companies with lots of workspaces it will clea...
Hugh Ainsworth
10 months ago
in Features
0
Future consideration
Do not count "will not implement" requirements in feature effort estimate
What is the challenge? If a requirement is listed as "will not implement" the detailed estimate is still counted in the feature effort calculation What is the impact? Currently need to manually adjust requirements to 0, in ADO if we mark the user ...
Guest
over 1 year ago
in Features
1
Future consideration
I was following this idea but was dissapointed that the calculated fields are limited to worksheets. I would need fields that are visible directly in Features and feature cards that are the result of a simple operation of other number fields, eith...
David Desrosiers
almost 6 years ago
in Features
2
Future consideration
After you've been using Aha! for a while, the number of epics builds up. This can be come a hinderence when you are looking to add a feature to an epic and the drop down list has dozens of results. After speaking with Aha! engineers, it was pointe...
Guest
about 5 years ago
in Features
1
Future consideration
Many times we come up with ideas that is related to multiple product like .com and mobile. It would be awesome if we could associate one feature and /or idea to multiple products using cloning.
Guest
about 11 years ago
in Features
1
Unlikely to implement