When using master releases, it is not possible to select the release template for the sub-releases to be created. Which means the workflow to date looks like this:
Create a master release
Resist the temptation to select the products in the produc...
Guest
over 9 years ago
in Releases
12
Future consideration
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
Bonnie Trei
12 months ago
in Releases
1
Future consideration
Roadmap history: Show when delivery risk flags were raised or removed
Who would benefit? Product teams tracking delivery risks What impact would it make? Teams often need to understand not just what records are currently at risk, but when the risk was raised (and by whom, when relevant) and when the risk was mitigat...
Reilly O'Connor
10 months ago
in Roadmaps
0
Future consideration
Epic/Feature boards using custom fields than versions
What is the challenge? Today we are not using Aha! out of box Releases and using a custom field for Release at Enterprise wide. So existing Aha! boards is forcing us to create versions at workspace but ideally we would like to use our custom field...
Shiv Shankar Vedharajan
2 months ago
in Workflow boards
0
Future consideration
When cloning, please provide ability to clear values in custom fields before saving in Domain Epics/Epics
What is the challenge? User clone records, without cleaning the existing data that is not applicable for the new record. What is the impact? Data consistency and re-work Describe your idea Have an option, when cloning to reset all the other attrib...
Edgar Holguin
2 months ago
in Epic
0
Future consideration
Map github username with aha emails for github-aha integration assignees sync
What is the challenge? aha-github assignees integration do not work What is the impact? cannot make use of the assignees sync in the integration Describe your idea In the Aha! Github integration the assignees are not getting synced. In Github we h...
Ankit Bapat
7 months ago
in GitHub
0
Future consideration
We have Improvement tickets in JIRA that we now (as new AHA users) want to migrate to ideas in JIRA. I have the JIRA integration created and would much prefer to import using the integration vs exporting tickets to CSV and then importing manually ...
Alex Horan
over 7 years ago
in Ideas
9
Future consideration
Copying an epic should also copy the associated features
Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense.
doug evans
over 5 years ago
in Epic
8
Future consideration
In this use case, ideas for multiple products are gathered in a single portal and linked to a single workspace for triaging. The team wants to filter the exploration view by custom fields. In particular, these are custom fields created for product...
Dale Potter
over 1 year ago
in
0
Future consideration