Skip to Main Content
ADD A NEW IDEA

All ideas

Showing 6239

Ability for a user to see what permissions they have

Our Aha! admin team frequently gets asked "Do I have a paid seat and which workspaces do I have edit permissions for". And so every time, someone from the admin team has to go take a look in the user admin area and report back. This causes an unne...
Steve Dagless 9 months ago in Account settings 0 Future consideration

Ability to edit default terminology in report column headers

The default terminology of column headers of reports is not always explicitly clear on what it represents, which leads to confusion both internally and with customers when these report are shared out. As an example, clicking on an Organization pro...
Jeff Shaffer about 1 year ago in Ideas 4 Future consideration

Add Epic as a filter for dashboards

During planning phases we have different teams managing their own epics that are a part of an initiative. Currently we can filter a dashboard by Initiative, but we can not drill into the epic level using that same dashboard. Ideally it would be gr...
Chris Eichermüller about 2 years ago in Reports 1 Future consideration

Assign portal users to an organisation and limit votes to the organisation instead of user

We currently allow multiple users to join our ideas portal from the same organisation, this is due to different members of that organisation specialising in different fields and thus having different ideas based on their profession and different t...
Guest about 1 year ago in User management 0 Future consideration

Include Area Path in VSTS Integration

I really like the VSTS integration 2.0, however could you add Area Path to the list of available fields that can be mapped to. This would be useful as in VSTS we use Area Path to note which dev team has picked up a feature and it would be great to...
Guest almost 6 years ago in Azure DevOps Services and Server 3 Future consideration

Ability to change the row height on Roadmaps

With roadmaps that contain a lot of information the gaps between the bars is to wide, and being able to reduce the size of those gaps would be useful in bunching the information up closer.
Andrew Brooks about 4 years ago in Roadmaps 8 Future consideration

Duplication of data in pivot report

There is a duplication issue when creating a pivot report at the epic level when you add in a multi-select field from associated features. The report in question is used to provide leadership with insight at the epic level, but we want to include ...
Annika Hudson over 2 years ago in Reports 2 Future consideration

Ensure labels are always shown on custom roadmaps

Currently, with the "Fit" option selected, there are record names on a custom roadmap that I can't see (because I can't scroll any further to the right). If this setting is intended to make the data "fit", the labels should also fit. Otherwise I h...
Reilly O'Connor 9 months ago in Roadmaps 0 Future consideration

New features created via an ADO integration are assigned to the parent epic release by default

Key problem: the "Parent" field in ADO can contain only one value. In ADO, a feature is automatically associated to the same theme as its' parent epic, but in Aha! this is not the case. So when features import, we associate them with the correct p...
Bryan McElhinney over 1 year ago in Azure DevOps Services and Server 0 Future consideration

Mermaid text generated diagrams

Allows much easier to iterate, more standard, and simpler to follow along version of diagrams/charts within documentation. GitHub and Notion have recently adopted the same library (mermaid) allowing for standardization across tooling.
Barnett Klane about 2 years ago in Application 0 Future consideration