Break the Product Family/Initiative Hierarchy Restriction
Currently you can only have as many levels of initiative hierarchy as there are Product Family/Products. But in tools like Version1 or Jira, the Epic structure is not similarly restricted – I can create as many levels of Epics as I want in V1 (I a...
Guest
over 9 years ago
in Application
0
Unlikely to implement
Allow blocking off time periods when release should not be shipped (promoted to production).
In our operations, we have some periods where no changes are permitted in production. It would be beneficial to add blackout periods so that any release dates within the blackout periods can be highlighted/reported.
Guest
over 9 years ago
in Reports
0
Unlikely to implement
Show all Releases in One Click (Roadmap --> Timeline) and show all in Saved View
Every day that I go into the Roadmap --> Timeline, I have to check to make sure that all releases are enabled, otherwise I run the risk of overlooking a release. In addition to being able to select all releases quickly, I would like the ability...
Guest
over 9 years ago
in Releases
1
Already exists
Stop auto-reformatting text for Customized Terminology
When using custom terminology per product, Aha! automatically reformats text, capitalizing/not capitalizing and adding an "s". The customized terminology would be much more beneficial were it truly customizable.
Kelly Killeen
over 9 years ago
in Account settings
5
Will not implement
I need to be able to attach a file, to a customer layout of a Change Request Epic (Master Feature) in order to ensure finance data is populated and held against the Change Request. This is a standard form and I would like ot be able to have that f...
Becca W
over 4 years ago
in Epic
0
Future consideration
Hi there, I have identified a problem that might be good to find a solution for. When using workflow view, default swimline setting is based on user picker. It would be a quick win to have a button that would automatically pick users that have ass...
Daniel Pokrývka
over 4 years ago
in Features
1
Future consideration
Sometimes our QA or Doc teams will reject a requirement because they have questions or additional clarification is needed. Once they are satisfied with the requirement they would like the ability to go back and approve it. This way we don't have t...
Sikia Soller
over 4 years ago
in Features
0
Unlikely to implement
Aha scorecard screen view access for viewers/reviewers
We are sharing the features with the devTeams and we believe that the rating information gives them the understanding on the value/importance of the feature (in our case it is a WSJF sorted out calculation, so they could see which was the business...
push the columns out so the Feature details slideout screen doesn't cover them (Features List view)
Right now you're using a CSS fixed position style, which slides out OVER the x-scrollable feature list. This means when you're looking at the details of the last two columns in the list, the details screen covers the columns, and the only way that...
Melissa Hopkins
over 9 years ago
in
0
Unlikely to implement