Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 946

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 over 6 years ago in Integrations 0 Future consideration

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

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

One epic in Jira

When creating integrations to Jira (master features and features to Epics and stories, within in several Jira board in the same instance) the first created epic in Jira should be the only epic created. Not one per integration/Board. At it is set u...
Guest over 3 years ago in Jira 0 Already exists

Jira 2.0: modify integrations based on templates

In 1.0, when using a template, you could choose what fields/behaviors to inherit from the template, and which to customize for that particular integration. This was useful for custom fields (now using a constant in 2.0) which will change from prod...
Max Cascone almost 7 years ago in Jira 6 Already exists

Align release with Jira sprints

Have the option in the integration settings to sync release with sprints in Jira There is no current way to represent a sprint in Aha yet that is how most people develop these days Currently whenever I move features between releases I have to manu...
Guest over 3 years ago in Jira 0 Unlikely to implement