Collapse / Hide Fields in Features Roadmap when Empty
Who would benefit? Consumers of roadmap What impact would it make? Increased engagement How should it work? Collapse / Hide Fields in Features Roadmap when Empty
Beau K
about 1 year ago
in Roadmaps
0
Future consideration
Who would benefit? Billing admins What impact would it make? Reduce friction/need for reaching out to support How should it work? Within Account > Billing, admins should be able to see the upcoming invoice including date and amount.
Terri Salie
about 1 year ago
in Account settings
0
Future consideration
Allow record owner to edit and delete other users' comments on that record.
In our use case, we manage work and collaboration using Comments in Aha records. Many collaborators add comments and we are working with a large number of records. To focus discussion, it would be helpful to be able to edit and delete comments, bu...
Integration between Aha! and Jira Align (formerly Agilecraft)
Jira Align is a requirements tracking platform that was formerly Agilecraft, and is fully integrated with Jira. Our teams that are using both Jira and Jira Align are mapping their Epics in Jira to parent Epics in Jira Align, so that the roll-up pr...
Adam Zoghlin
over 3 years ago
in Integrations
1
Future consideration
Allow mapping Release as a field on Requirements in Azure DevOps integration
Due to our iterations setup in Azure DevOps (ADO) we do not currently map Releases as a record. We are sending this instead as a field on the Epic and Feature records to a custom field in ADO. We would like to do the same on Requirements but it is...
On the Product Overview page, it currently shows Features and Releases.
I would also like to see active Initiatives for the product on that page.
I tried setting up a custom field, but that is to choose initiatives to attach, not to show currentl...
Max Cascone
almost 8 years ago
in Strategy
0
Already exists
Within the organisation I work for, only administrators get product owner privileges. This is to save the product owners from themselves when it comes to integrations, workflow settings, navigation and terminology.
However, doing this restricts th...
Project Parker
over 6 years ago
in Account settings
0
Future consideration
I've recently started to use requirements within features more - and see them as a good way to clear a lot of unnecessary detail from feature overviews / reports. However to change a large number of features into requirements is a slow one-by-one ...
Guest
almost 9 years ago
in Features
4
Already exists
Who would benefit? product managers What impact would it make? make the my work section more clean for ideas How should it work? the ideas are promoted to backlog they should not appear in the idea section anymore.
Guest
about 1 year ago
in Ideas
0
Future consideration
Navigation item for release should match default terminology in non-product workspaces
Who would benefit? Teams using non-product workspaces What impact would it make? Avoid confusion due to different terms used How should it work? The navigation item for release should match the default terminology if the terminology wasn't customi...
Chrissi McNamara
about 1 year ago
in
0
Future consideration