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...
Jennifer Lange
over 1 year ago
in Development
0
Future consideration
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 ...
Nigel Lawrence
over 1 year ago
in Notes
0
Future consideration
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 ...
Guest
almost 9 years ago
in Application
9
Unlikely to implement
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...
Max Robbins
over 1 year ago
in Capacity planning
0
Future consideration
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 ...
Austin Merritt
over 6 years ago
in Asana / Integrations
4
Future consideration
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 ...
Guest
11 months ago
in Features
1
Future consideration
Aha! Scorecard on Release apply to Master Features and Features
Title. Allow an "Aha! Score" which is applied at the "release" level to allow apply and synchronize to the "linked" Master Features / Features for Product Workspaces.
Guest
about 4 years ago
in Releases
2
Future consideration
Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...
Allow Default capacity Planning to be inherited from company
It would be great to set the option for capacity (time/point) and also if to capture at task or feature level, so when I add a new product it is already set. AS it stands, every new product I have to go in to config, turn it on, and switch from ti...
Jon Ellis
over 6 years ago
in Application
1
Future consideration