Dear Team. We would like to create releases centrally for our entire Product Suite consisting around 20 workspaces. You advised me to consider the roll-up releases function which is great still we have to define our own unified release names manua...
Krisztina Hodjan
almost 5 years ago
in Releases
0
Future consideration
Allow creation of new entries in Many to One custom table
I love the custom table functionality, but there seems to be no way to add a new entry from the feature itself. I have to go to the custom table and add a row that way. It would be much nicer if I could just add a new record via the selection box ...
Guest
almost 5 years ago
in Features
0
Future consideration
Recently integrated SSO with Aha! (thank you Chris!). we're now going to transition users from traditional password to SSO. I think there are some small changes you can make to user administration to make this easier. Should be able to search on t...
Show only selected product when filtering by Goal Name
When filtering by Goal Name, such as on the Features Board, the list of goals to choose from includes all goals from all products. When your visible product line space includes over 50 products, the list of goals becomes really long. This makes se...
Dan Eisenhut
over 7 years ago
in Features
0
Future consideration
Allow roadmap time frames to be set to a rolling period
For organizations that want roadmaps to reflect an ongoing rolling time frame, allow the time period selection to be able to specify rolling periods so the time period on the roadmaps/reports don't have to be continually updated. For example, I wa...
Guest
almost 5 years ago
in Roadmaps
0
Future consideration
It would be great to allow for cards (epics, features, requirements) to move in any "card" based view. A great example is Google Keep (Web version on Desktop). Google Keep allows for easy moving of cards and pinning of favorites to the top. Add in...
Todd Materazzi
over 2 years ago
in Features
0
Future consideration
better validation warnings and units tips and handling on estimates fields
the toolips on estimates fields need consistent messaging in all field contexts, with proper messaging/tip content based on the units of the configuration. this needs to be the UX when creating (actual configured units not a hard-coded either/or t...
Kevin Martin
over 2 years ago
in Capacity planning
0
Future consideration
please let admin better control the field choices on apply rank to users cannot make bad choice
apply rank opens a picker to let user decide which custom field to apply the rank value to , and that custom field needs to be the field in the mappings that provide update into target tooling (my case, its ADO, stack rank). I see multiple custom ...
Kevin Martin
over 2 years ago
in Roadmaps
0
Future consideration
It would be nice to filter (AND, OR, NOT, etc) for specific pre-set tags within a custom field. For example, if I got a custom field called NUMBERS. Within that field I've pre-defined "1", "2", "3", "4". These numbers are assigned to a requirement...
Simon Au
almost 5 years ago
in Reports
0
Future consideration
Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter
almost 5 years ago
in Jira
0
Future consideration