All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6307
7
VOTE
Having flexibility around Release Dates being either inherited from Rollup release or manually populated
We rely on Rollup releases quite a bit, however, from team's Feature board perspective it's often helpful to track "product" releases info, especially dates and be able to expose those accordingly. At this point, since we're using Roll up releases...
2
Future consideration
17
VOTE
I want the external release date to match the internal release date but still round to a time period such as quarters.
Right now if you set the external release date to be the same as the internal release date then the external date moves with the internal date. I would like an option that when you are rounding an external date that it can also update the date to ...
3
Future consideration
1
VOTE
Tab ordering when adding a requirement makes it difficult to return to the title
Who would benefit? Keyboard users What impact would it make? Improve requirement adding experience. How should it work? When adding a new requirements, when you press shift + tab from the description field, it should go to the title and not the pr...
0
Future consideration
1
VOTE
Allow selection of which dashboard filters to use, instead of just on/off "use dashboard filters"
Who would benefit? Anyone merging information from different workspaces, timeframes, or other categories of data. What impact would it make? Allows one dashboard to be more flexible for multiple use cases. How should it work? Instead of a single c...
2
Future consideration
8
VOTE
Strategic Roadmaps Custom appearance for Epics and Features
As a stakeholder I want visual clues to differentiate between epics and features. Since nested views are not available in Strategic roadmaps, it would be great to change appearance of epics to help stakeholders who are not as familiar with the vie...
2
Future consideration
16
VOTE
Allow alignment control of text, numbers and data in any report
Some reports in Aha are great and others look bad because the data is aligned left by default with no control options. So say a single number for votes aligns left but the column header could be long and it makes the report appear poor quality
2
Future consideration
20
VOTE
7
VOTE
Allow templates to be applied to records after they're created
When records i.e. epics or features are created in the user story map or starter roadmap view, they do not have their record templates applied. This is because you cannot select the feature type within that view upon creating the record. In cases ...
2
Future consideration
4
VOTE
Allow team leads to manage workspace releases
Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...
0
Future consideration
5
VOTE
