ADD A NEW IDEA

Application

Showing 7521

Increase the maximum number of records returned by the API

Who would benefit? Users who are using the API to build reporting out of Aha! (e.g. Power BI) What impact would it make? It would reduce the number of API calls that need to be made to retrieve large amount of records How should it work? Instead o...
Nicolas Andrillon 8 months ago in API 0 Future consideration

Allow sorting pivots by other fields when only description is displayed

When creating a pivot report and using the description field of our release phases to group records as columns, we are unable to select another field to drive the sort order. The application only allows us to sort alphabetically by the description...
Michael Judge 8 months ago in Reports 0 Future consideration

Ability to set a default landing page per workspace

When using a centralized workspace for Ideas, it can be confusing for users to navigate to other pages like the Features board when going to the Ideas workspace from another workspace. In some cases users are taken to sections of the navigation th...
Stephanie Lechner over 1 year ago in Account settings 0 Future consideration

Aha! Automation Needs Improvement

I have a mandatory custom field in Aha! Feature’s form and I would like the field to be non-editable once the release is approved through fixed workflow statuses, so that people could not make any changes there and any exception changes should go ...
Ankush Kumar over 1 year ago in Features 1 Future consideration

Update API integrations with JIRA to add Created Date and Resolved Date

We would like to be able to map the created date as well as the resolved date to fields within aha from JIRA.
Guest about 3 years ago in API / Jira 1 Future consideration

Allow pie charts to fully display in a smaller sized panel within Dashboards

It seems like whenever a pie chart has been added to a dashboard, you need to expand the panel until the full chart is visible. There also seems to be a lot of white space in the chart background. It would be great if this could be reduced.
Shumona Raha over 1 year ago in Reports 1 Future consideration

Restrict broadcast messages to specific Product Line(s)

In our large organization, we have three top-level Product Lines to represent each corporate division. Some broadcast messages are useful for the entire organization, but others would be more meaningful if they were visible to users of a specific ...
Gary Spencer over 9 years ago in Comments / Notifications 7 Future consideration

Allow Name Search at Master Feature (Epic) Level

What is the challenge? Feature available at Feature level is not available at Master Feature level What is the impact? time consuming to search for items Describe your idea Allow Name Search at Master Feature (Epic) Level
Alex Berestenko 4 months ago in Reports 0 Already exists

Report on custom fields used in integrations, reports and roadmap views

Today you can identify which layouts and workspaces custom fields are actively used in. However, when looking to manage a large number of custom fields across a large organization, there is no way to determine which integrations are using that cus...
Jeanette Resnikoff over 1 year ago in Account settings / Reports 0 Future consideration

New User Story Map entered Epics should still require required fields and load the standard description field template

Problem: When adding entities (e.g., Epics) via the User Story Map, the user is not prompted to enter in required fields and the predefined Epic template is not loaded in the description field. This bypasses the Epic creation protocols elsewhere i...
Peter Bongiorno almost 3 years ago in User story map 0 Future consideration