All ideas
Sort by:
Trending
Status:
Showing 9173
8
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
3
VOTE
Support automations that trigger only for active sprints
We have automation set up to notify by email when a feature gets added to a sprint. Is there a way to refine this to “added to a sprint in progress”? When we close out a sprint, and we have items that roll to the next sprint we get emails for each...
0
Future consideration
3
VOTE
Improved management of document template catalogue
Who would benefit? Notebook users, Enterprise standards management What impact would it make? Users would be able to identify the templates being endorsed across an organisation in creating new documents How should it work? I see 2 very desirable ...
0
Future consideration
20
VOTE
Allow reusing prefix for products and product lines
I accidentally changed the prefix for one of the products and now it won't let me reuse the previous prefix. Also once you change the prefix for a product, it doesn't update the existing records. It should allow for a prefix to be reused and also ...
9
Unlikely to implement
11
VOTE
3
VOTE
Capacity report - do not show logged work on a view of initial estimates only
Who would benefit? When initial estimates are used for capacity, logged work on records does not adjust planned work accordingly and this causes an inaccurate capacity report. Removing logged work from initial estimate view of capacity report will...
0
Future consideration
15
VOTE
Allow for mapping to-dos in Asana integration
In some cases, Asana sub-tasks are more closely related to Aha! to-dos than requirements. For example, a feature may have to-dos related to marketing tasks which need to sync with Asana.
An option to map To-dos to Tasks or Subtask would provide a ...
4
Future consideration
2
VOTE
Do not count "will not implement" requirements in feature effort estimate
What is the challenge? If a requirement is listed as "will not implement" the detailed estimate is still counted in the feature effort calculation What is the impact? Currently need to manually adjust requirements to 0, in ADO if we mark the user ...
1
Future consideration
9
VOTE
5
VOTE
© 2025 Aha! Labs Inc.•All rights reserved