Assign an epic to two initiatives. We can have a piece of work, e.g. update master data, that can contribute to more than 1 initiative. I tested it out and if you add an epic from another initiative, it moves it rather than adds it
Guest
about 2 years ago
in Epic
0
Future consideration
Idea status automatic change when linking to an existing feature
If you link an idea to an existing feature the idea status should automatically change to "planned" like it does when you promote an idea to a new feature.
This creates manual processes and it can be confusing for the idea reviewers.
Guest
about 8 years ago
in Ideas
0
Unlikely to implement
Calculate progress based on completed status of child records
I would like the option for Aha to automatically calculate the progress of an Initiative based on the number of Epics or Features that are Released verse still open. The same would apply to Epics and the child features.
Terry Blok
about 2 years ago
in Account settings
2
Future consideration
Ability to include multiple record types within the cells of the pivot report
In order to have a pivot report for long term roadmap that its columns are timeframes (e.g. FY23 Q3, FY23 Q4, FY24 H1, FY24 H2, FY25) rows are workplaces for example (or any other custom field for describing the domain) cells are records that can ...
Ronit Binshtok
about 2 years ago
in Reports
0
Future consideration
The Ideas list view allows me to filter ideas by the date range a specific status change happened (eg. changed to 'Incoming' or changed to 'already exists') . I would like to be able to filter my list of ideas that had any status change in a given...
Only send Aha Feature Name to Jira Summary once - while not breaking Integration 2.0
My use case is the following: Product wants to shorten the Aha Feature Names so they look better in Aha's roadmap views.
On the other hand, I don’t want Aha to overwrite my more descriptive Summary on my Jira tickets.
How do I set up the integrati...
Guest
about 6 years ago
in Features
0
Future consideration
We are working with multiple products (one for eacht customer) and a number of releases per product. To manage the daily work, we use the calendar view for features.
It should help a lot if the amount of capacity for the features on a specific ...
Guest
about 6 years ago
in Reports
0
Unlikely to implement
The History for linking and unlinking features to master features.
We need a way of identifying any scope creep by viewing the history of a master feature to see if any new features have been linked to it.
This functionality is available at a feature level as you can see all requirements that are linked to it.
We have two portals, one is customer-facing and the other is internal. I'd like to be able to set the internal portal to allow all users in that portal to edit all ideas and custom fields. This would allow them to refine requests when they are add...
Amanda S
about 4 years ago
in Ideas portal
0
Future consideration