ADD A NEW IDEA

All ideas

Showing 9001 of 9001

Tags should propagate bidirectionally into Pivotal Tracker

Much like status, it would be nice if tags on features would propagate instantly to stories in PT bidirectionally. We have historically used PT labels to organize aspects of our sprint. It would be nice to setup initial tags in Aha and have those ...
Jason Novek about 9 years ago in Pivotal Tracker 2 Will not implement

Ability to map personas to a step in story maps

A step in a story map is typically assigned to a specific role. Currently I do not seem to be able to show or link the persona to the step
Arjen Bos about 5 years ago in User story map 0 Unlikely to implement

Support mapping JIRA Tempo Account field

When using the JIRA Tempo plugin to track work time, it is useful to link issues to Accounts - for this the plugin exposes a custom field named Account. This field, formerly called Billing Key, is used among others in reporting, to decide which cu...
Guest about 9 years ago in Jira 8 Unlikely to implement

Ability to show more release details on the feature board

In the feature board view, the top of each release column shows very limited information today. Just release name, release date, and capacity. It would be useful to show more information about a particular release at the top of each release column...
Andrew Foster over 1 year ago in Releases 1 Future consideration

I want the external release date to match the internal release date but still round to a time period such as quarters.

Right now if you set the external release date to be the same as the internal release date then the external date moves with the internal date. I would like an option that when you are rounding an external date that it can also update the date to ...
Guest over 7 years ago in Releases / Roadmaps 3 Future consideration

Allow for export of custom roadmap to PowerPoint

Most corporate presentations are given in PowerPoint. Currently we need to export as PNG or PDF and then cut/paste into our power point slide show.
Guest over 3 years ago in Roadmaps 1 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 about 2 years ago in Azure DevOps Services and Server 0 Future consideration

Make hierarchy reports resilient to product hierarchy changes or provide a method to preserve hierarchy report definitions

We modified our product hieararchy to support single sign on (SSO) for Aha. (The reason we had to change the product hierarchy for SSO was that the company was acquired after we started using Aha.) A knock-on effect of changing product hierarchy w...
Perri-Anne Sims over 5 years ago in Reports 2 Future consideration

Custom Fields Permissions

When creating custom fields for ideas or features we need ability to select which user group has rights to edit it. We created a field named owners, with multiple select options from which a product owner can select several names of people that ow...
Guest about 10 years ago in Account settings 6 Unlikely to implement

Display features board card color based on type instead of status

We use different feature and epic types and would like to have the option to color the cards on the features/board based on the type instead of the status for easier visual distinction of each card's type.
Scott Bleasdell over 2 years ago in Features 0 Future consideration