Jira

For Epics which get initiated in Aha and flow down to JIRA, we want to enable 2-way integration so that updates which happen in JIRA are realized in Aha. However, if a NEW Epic is initiated on the JIRA side, we may not want that to be visible in A...

When using the requirements level estimates to drive the total estimate on the feature level we would like the feature level estimate to be reduced when a requirement is marked in a complete status. Also we would like to have the feature status au...

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.

If I update a Requirement after the Feature has been synced to JIRA, I want to be able to immediately have the corresponding Story in JIRA updated to match it. The synchronisation seems to take more than 10 minutes to go through. Like we have Acti...

Currently: With the JIRA 1.0 integration. When using Requirements for Time Tracking the "Total Time" is not displaying the correct data. In Aha the Time Tracking says 73d 4h. Screenshot "Aha Time Tracking.png" In Jira the Time Tracking says 2w ...

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...

I'd like to see the Aha!/JIRA integration be updated to have an option to set dates of features (and possibly other items) based on Status that is in JIRA. Example: I create a Feature in Aha! and integrate/export to JIRA When Feature (referred t...

Integrations 2.0 - Please only show valid integration directions for Release <-> Fix Version. I had opened ticket https://support.aha.io/hc/requests/176083 because I could not connect to the Jira version using Actions > "Link with existin...

In integrations 1.0 if I mapped Features = Story Requirement = Task Aha! would send the records to JIRA and create a "Relates to" dependency between the Story and the Task to visualize in JIRA that the two records should be related to each other. ...

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...