All ideas
Sort by:
Trending
Status:
Showing 9073
1
VOTE
1
VOTE
2
VOTE
In Ideas portal, flexibility to provide conditional logic wherein dependency exists with an Epic/feature. We are using Ideas for leveraging Dependencies.
What is the challenge? Users create ideas, without there is a proper dependency What is the impact? Data discrepancies, because users omit to include dependencies to other records Describe your idea Allow conditional logic, to make mandatory depen...
1
Already exists
2
VOTE
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...
0
Future consideration
2
VOTE
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...
0
Future consideration
94
VOTE
Support release templates for rollup releases
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...
12
Future consideration
10
VOTE
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) ...
1
Future consideration
8
VOTE
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...
0
Future consideration
2
VOTE
Keep formatting from a Jira table
What is the challenge? The Jira integration does not currently support the table markdown syntax What is the impact? The result is a formatting issues when a record including a table within the description is synced to Aha! via the integration Des...
0
Future consideration
6
VOTE
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...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved