Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 949

VSTS updating Aha! features base user stories

Leadership and executives are using Aha! more and more. Having the ability to represent the percentage completed of features in a given release is very important when reporting to large audience. I like to ability to show the percentage of the Fe...
Guest over 6 years ago in Azure DevOps Services and Server 0 Already exists

Ability to set defaults for Record Link

For nearly all Record link items we use Contains/Features. It would be great if we could set those by default. A hassle to always have to use the drop downs
Thomas Cruse over 6 years ago in Integrations 0 Future consideration

Integration last used field

To enforce usage of Aha when communicating priorities and reporting progress against developing those priorities, want to see the last time updates were sent to/from Jira so we can track against that date.
Danielle A over 3 years ago in Jira 0 Future consideration

Pivotal Tracker: 2 way sync for Requirements — not just Features

Today PT can only update status in Aha for Features. We'd like to have it update the status of requirements as well. In our case, it's particularly useful because we map Aha Features to PT Epics (and Aha Requirements to PT Stories). So we're blin...
Yok Tan almost 10 years ago in Pivotal Tracker 2 Already exists

Integrate with JustInMind

A large part oft he PO process is creating Wireframes, Mockups, and Prototypes of software. The PO can often times work very closely with a UX team to create prototypes to get a project greenlit. There are many UX tools but JustInMind has become o...
Aaron Bawcom almost 10 years ago in Wanted 0 Unlikely to implement

Trigger status change based on record % complete

E.g. if engineering has reported that 100% of work on a release is complete via the Jira integration, update the status to 'ready to ship'
Danielle A over 3 years ago in Jira 0 Future consideration

Import Feature Requirements from Jira 2.0

It would be helpful if Requirements were built out so that they can be imported from jira 2.0 AND moved from feature to feature as easily and features are moved betweeen master features.
Kaylee gervasi over 6 years ago in Jira 0 Already exists

Add a "Two way integration" (set once)

Please add a "Two way integration" (set once) feature in Integrations 2.0. Use case: the Feature Name (in Aha) and its corresponding Summary (in Jira) are not always the same. For example, the name in Aha is usually short so it shows well on the r...
Guest almost 7 years ago in Integrations 0 Future consideration

Manual selection of items selected for import from Jira

As a user of Aha! and Jira I want to be able to select the items that get imported from Jira so that I can more easily coordinate and synchronise the data held in the two products. There are two main tools that allow data to be brought into Aha! f...
Guest almost 7 years ago in Jira 0 Unlikely to implement

The JIRA/Aha integration does not sync tags or releases (even when configured).

No description provided
Guest over 3 years ago in Integrations 1 Already exists