All ideas

Showing 1526

Support all types of JIRA text field formatting

The current JIRA integration doesn't support renderers other than the Wiki Style Renderer very well. Please add support for the other renderer types.

Guest over 8 years ago in Jira 0 Unlikely to implement

5 VOTE

Show Release Phase as Available Field to Include on Feature Custom Layout

In creating a custom feature layout for use within a product, the release is shown by default but there is no way to show the Release Phase. The only way that you can then assign a release phase is to drop down the ellipsis, Link to Release Phase,...

Lexy Kassan almost 6 years ago in Features 1 Unlikely to implement

8 VOTE

In pivot table column headings use natural order for custom field values

If a custom field has pre-defined values, then order the headings by the order of those values.

Chris Waters over 9 years ago in Reports 1 Unlikely to implement

6 VOTE

AHA! Should share a public version of its roadmap so that users can know what changes/features are planned and when they are planned for

There are plenty of features I wish AHA! would have, and when I look at the ideas portal, some of them say, "likely to implement". What does that mean in terms of timeline? How long of a roadmap does AHA keep? These questions could be answered if ...

Oleg Yazvin about 7 years ago in Application 0 Unlikely to implement

7 VOTE

Auto-populate assigned Person from feature level to to both requirements and To-dos

When assigning a person to a “Feature”, we would like an update/option that also auto-populates that same person in the requirements and To-dos within that feature.

Guest over 8 years ago in Features 2 Unlikely to implement

5 VOTE

Need the ability to add COMMENTS to a Release Template

I need the ability to add Comments to a Release Template. By adding a static comment to a Release Template, I would be able to provide additional instructions to the end user regarding the use of the template, links to additional information, an...

Joe Carpenter almost 6 years ago in Releases 1 Unlikely to implement

6 VOTE

Make To-Do's a "first class feature" in Aha!

This idea encompasses a big picture echoed in a number of idea requests. The To-Do' feature in Aha! really seems to be an afterthought compared to the other record types in Aha! such as Goals, Initiatives, Features etc. Specifically To-Do's don...

Jeff Shood about 7 years ago in To-dos 2 Unlikely to implement

5 VOTE

When moving a feature from one release to another, the progress should not count against the capacity of the new release.

Often times a feature is not completed within a given release, and it must be moved to the next release. Currently, if a feature has an estimate of 100p and 50p are completed in one release, then that feature is moved to a new release, all 100p ar...

Guest about 6 years ago in Releases 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 over 9 years ago in 0 Unlikely to implement

6 VOTE

Option to remove requirement of an email address when submitting an idea

Using Aha! to build out a survey in the Ideas Field and would like to remove the requirement for users to have to enter their email, so users could feel as if the ideas are anonymous.

Guest over 7 years ago in Ideas 1 Unlikely to implement

Share your product feedback

Please enter your email address

FILTER BY CATEGORY