All ideas

Showing 1374

Allow Aha Idea ID to be Mapped to JIRA

Once requests are sent to JIRA there is no quick way to see the original Aha Idea source for the ticket. We would like to have the Idea ID exposed as a custom field so it can be mapped to JIRA. This will allow personnel working on the JIRA ticket ...

Guest over 8 years ago in Ideas 0 Unlikely to implement

8 VOTE

hashtag mention includes the id and name of item for readability

When # mentioning something, it could include the id + the name in the link to the item.

Guest over 8 years ago in Application 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 almost 9 years ago in Reports 1 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 almost 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 over 6 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 almost 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 about 10 years ago in Releases 1 Unlikely to implement

8 VOTE

Broadcasts - Add start and expiration date fields

Please consider creating a start & expiration date field for broadcasts. This would be useful so that the admin can 'schedule' the messages and store future messages for delivery. If implemented, please include timezone so the admin knows exac...

Joe Carpenter about 9 years ago in Account settings 5 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

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 almost 8 years ago in User management 2 Unlikely to implement

Share your product feedback

Please enter your email address

FILTER BY CATEGORY