ADD A NEW IDEA

All ideas

Showing 8638 of 8638

Dependent Reports/Subreports

Currently if a report is being used in a large org by multiple teams, there's no clean way for each team to view a version of that report that is relevant to them. They can change the filters on the report but those then impact every other team, w...
Sweth Chandramouli over 3 years ago in Reports 0 Future consideration

Option to Automatically add New Features and release to roadmaps

I am often times using that roadmap not only as way of visualizing the data but as the principal tool in which I can see all my projects and products at once, gain insight into the global picture of the work that is being done and then changing st...
Jay Altschuler over 5 years ago in Reports 0 Future consideration

Bulk delete custom table records

When cleaning up custom table records, it is sometimes necessary to delete many records at once. It would be nice to be able to delete these records all at once.
Austin Merritt over 5 years ago in  0 Already exists

Use Epic Estimates option on Initiative

As a Product Owner who reports on the strategy initiatives, I would like for my "estimate" field on the epics to roll up to the Initiatives "estimate" field in a similar manner as Feature estimate's roll up to Epic's estimate field with the "Use f...
Guest almost 2 years ago in Capacity planning 0 Future consideration

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 almost 3 years ago in Integrations 1 Future consideration

Improve handling of progress calculation for Develop team work

Features should have a single continuous flow that progresses from Design through Dev and QA, where statuses pick up where the last team left off. I.e., the final status of the record for the Dev team would be “Ready for QA” and map back to a simi...
Guest 11 months ago in  0 Future consideration

Enable Aha! community bulletin board for Aha! community

It will be helpful to reach out to (focused reach) all Aha! clients and inquire who solved the problems I am encountering. For example, instead of searching ideas and hoping Aha! solves a problem / blocker - others in the Aha! community may have a...
Todd Materazzi 11 months ago in Application 0 Future consideration

Automation to Create Duplicate Record in Another Workspace

We have multiple teams who work in multiple workspaces where one body of work being created may trigger another body of work to be created. Currently we need to copy the record and then move the copy to the other workspace. Ideally we would be abl...
Kristina Ursin almost 2 years ago in Features 0 Future consideration

Export views to Keynote

In addition to exporting views to PDF, tt would be helpful to export views to Keynote.
Craig Pflumm almost 3 years ago in  0 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...
Guest almost 3 years ago in Azure DevOps Services and Server 0 Future consideration