Feature dependencies based on Requirement dependencies
Our engineers have a good view into Jira issue dependencies. Our business process enforces that all Jira issues will belong to a Jira Epic. We then map those Jira Epics into Aha Features. We would like the Jira Story/Task/Bug dependencies to be ro...
We want to automate the user provisioning and make sure we don’t provision users beyond the allocated count.
Hence we want to leverage API to get the allocated user count .
Guest
over 6 years ago
in Features
0
Future consideration
It'd be really great to be able to see all outgoing emails that are sent along with a delivery/viewed status.
This would allow us to better support our customers by seeing/ensuring they receive our notifications and in allowing us to audit exactl...
Guest
over 6 years ago
in Features
1
Unlikely to implement
Ability to NOT include the Description Field for the Create Template
I am using the new Template capability to provide guidance for populating Initiatives / Capabilities (Features) via a standard format. Unfortunately, to use this feature I am required to include the Description field in the Create Layout. This res...
Peter Bongiorno
over 3 years ago
in Features
0
Future consideration
Make it possible to drag & drop features between releases in "Details" view
I have a long list of features that I imported for JIRA that I need to review and triage. I'd like to have the ability to quickly move something to a different release, and it doesn't appear to be possible to drag them to a different release when ...
Gabriel Michaud
almost 10 years ago
in Features
0
Will not implement
Remove Epic as mandatory field while a feature is created.
To create a feature I must link it to an Epic before I can save it, but then I can go back and unlink the Epic. If I can go back and unlink the Epic, then why not allow the user to create a feature without linking it to a specific Epic from the be...
Guest
over 3 years ago
in Features
0
Already exists
Support Initiatives Report View to include Changes of status with dates
In program reviews, it is incredibly helpful to be able to surface up changes on initiatives from previous meeting. Being able to have a change date like what features have would enable to provide a report or view of initiatives that have dropped ...
Guest
over 6 years ago
in Features
0
Future consideration
Add the work done field to the feature cards and feature details
When the features are displayed, it would be very helpful to see the work done field in each feature card and in the feature details.
Now if I want to see the work done, I have to click on the card and check the timetracking history
Guest
over 6 years ago
in Features
1
Already exists
I want to hit 1 button to duplicate & link, because it's sllloooowww to duplicate a feature and link it to it's original when I have to do it to a lot of features.
Guest
about 10 years ago
in Features
1
Unlikely to implement
As we plan our releases, we order features in those releases by their Aha! score. The "Rerank features by" option makes it simple enough to ensure records are in the correct order during planning. As a release plan evolves though, it becomes chall...
Jeff Tucker
over 3 years ago
in Features
0
Future consideration