It would be great to allow @mentions in features. I could see this being useful in: comments feature description requirements description For me this is a priority because otherwise it's hard to call attention to a feature to someone unless you ma...
Support parent-child moving across workspaces and Jira projects
In the Aha! we have Features that reference a parent Epic in another workspace. In Jira we have issues that are children of an Epic in another project. This cross workspace/project relationship is supported in Aha! and Jira, but the integration do...
Michael Bruner
over 3 years ago
in Integrations
4
Shipped
We use confluence as a platform for detailing product development plans. It would be great if one was able to embed notebooks from Aha! within confluence pages or indeed easily allow Aha! data to be inserted into confluence.
A set of macros, ava...
I have a numeric custom Feature field Priority. When I include it in a new pivot table, Aha! sorts the field alphabetically not numerically. ADDED: Ability to sort in general so that you can change the order in which columns (data) are ordered fro...
Ability to see ALL To-do items at a: Product or Product Line level. If able to drill down to Release level that would be ideal
Often we need to run stand up sessions or project checkin's and go through the 'To-do' items that are coming up, outstanding etc for the team. As you can have 'To-do' items at:
Product level
Product Line level
Release level
Feature Level
Require...
If you assign a JIRA issue to be unassigned, the assignee is not reflected in Aha! correctly which causes the next Aha! update to overwrite the unassigned status in JIRA with whatever the previous assignee was set to.
Trigger slack notifications based on updates to custom fields in aha
We use a custom 'Status update' field to track and communicate the details around current status of an initiative. This field is updated by the product management team weekly and/or whenever there are key updates (that may not require an actual "s...
We do not want everyone to get shipped release notifications. For example, if we have dozens of Reviewers and Viewers, they do not need these notifications. It is particularly challenging when first setting up Aha! and workflows as it can confuse ...