Ability to Configure Epic View as Default for all workspace views (Board / Priortization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
16 days ago
Prevent users from inadvertently moving Features' workspace
Who would benefit? Our company's 750+ workspaces What impact would it make? If not resolved, this can cause damage, manual work to re-create Aha! <> Jira integrations, and work becoming out of sync between the two. How should it work? We oft...
2 months ago
Show epics and features together on features board
By adding grouped features to the Master Feature view this would allow users to see which features are within their master features, and allow drag and drop of features between master features.
The display of features is currently not an optio...
over 4 years ago
Customize record cards -- this needs to be available for cards in whiteboard as well
Who would benefit? All Aha White board users What impact would it make? alleviate pain of going back and forth to look at ranking or priotization or other details How should it work? All the information in Customize record cards in at workspace le...
We need the ability to bulk copy selected records (e.g. epics / features). How we expect it is implemented We are aware that we can multi-select records on feature boards. After multi-selecting, we want to right click on the selected records and c...
7 months ago
Planning to implement
Automation Rules: Allow a Custom field of a related record to be updated to "MATCH"
We want to set an Automation Rule that will automatically set the value of a custom field at the feature level to "Match" the value in a custom field on the Epic. We also want the ability to make the value unchangeable on the feature - which we ca...
When we change Epics quarterly plan, user stories are being lost on the way
When we move Epic from one quarterly plan to another, if we drag them, it asks should the linked user stories be moved as well. However, if we simply change quarterly plan name in the field, user stories are not being moved. Same issue appears if ...
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.
almost 5 years ago
Who would benefit? User teams that do a lot of repetitive work with contextual differences What impact would it make? It would help keep backlog items consistent and reduce the time needed for repetitive work created with necessary data relationsh...
4 months ago