Aha! Roadmaps

Showing 1497

A pool of paid seats

Managing a large pool of seats is time consuming. Instead of trimming a list we'd like to define who can use the paid seat and then pay for a concurrent limit. So say we have 250 people in portfolio management (which could be defined by HR job rol...

Keith Mantell over 4 years ago in 1 Unlikely to implement

3 VOTE

Hillcharts for epics

I like using hillcharts to track the progress of work in an epic. I'd like support for this visualization in Aha! Develop.

Guest over 3 years ago in Agile reports / Epic 0 Unlikely to implement

5 VOTE

Allow steps box in Story Board to grow so you can see the entire step

When you add a step to a user story map if the text expands beyond the visible part of the box it is not easy to see the entire step. The box should grow in the same way as the feature box does.

Matt Garrett over 5 years ago in User story map 0 Unlikely to implement

8 VOTE

Ability to choose how each Aha Initiative/Feature/Requirement should be mapped to JIRA, as opposed to one mapping setting for an Aha product.

As a user, when creating a new Aha Initiative or Feature, I would like the ability to choose whether the Aha Initiative/Feature/Requirement should be mapped as a JIRA Epic, User Story, or Requirement, so that I can have more flexibility when creat...

Guest about 9 years ago in 0 Unlikely to implement

6 VOTE

Respect the product hierarchy in Reports

The starter roadmap can display objects (such as initiatives) in descending order according to their position in the product hierarchy. This is extremely useful when showing how high-level product line initiatives relate to lower-level initiatives...

Guest almost 7 years ago in Roadmaps 2 Unlikely to implement

7 VOTE

Allow auto-import of JIRA issue without the need for a "parent record" (or just a pre-defined default like with manual import)

I was a bit confused when I could import items from JIRA manually, and webhooks were working both way, but when I made a new issue in JIRA, it was not getting auto-imported. I read through lots of really long explanations about the need for "paren...

Guest about 8 years ago in Jira 3 Unlikely to implement

9 VOTE

Shipped releases should be archivable

After a certain period of time, it is no longer helpful to see a release that has been shipped. It should be possible to "archive" a release so that it no longer is visible in dropdowns, the release list, or the feature board.

Guest over 10 years ago in Releases 1 Unlikely to implement

8 VOTE

Default Release Phase

You should be able to set at default release phase for a release, so that all features added to this release ends up in the default release phase. This would gratly simplify and make the prosess more efficient. Now you have to move new features in...

Guest about 9 years ago in Releases 3 Unlikely to implement

8 VOTE

better redmine integration - requirements are children of features, and tasks are children of requirements

redmine integration is very helpful and needed. "When a feature is copied to Redmine one issue will be created for the feature. If the feature has requirements then each requirement will also be sent as an issue." there should be a way of re...

Michael Martini about 9 years ago in Integrations 0 Unlikely to implement

7 VOTE

Allow user to be deleted through API

Currently user can be only disabled through API. however there is no way to delete users from the portal no matter if they are disabled or enabled. Please add Delete option in the api for the user object.

Guest about 8 years ago in User management 2 Unlikely to implement

Share your product feedback

Please enter your email address

FILTER BY CATEGORY