Jira

In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...

As a user with an integration with JIRA, I want the ability to @ users in my feature, requirement, or comments in Aha and the @ will sync to the JIRA users available so they can receive a JIRA notification. Our dev team does not use Aha notificati...

In the 1.0 integrations I had configured it to not try to create new Aha! records when records were created in JIRA. I would like to be able to do the same in the 2.0 integrations. Currently when someone creates a new issue in JIRA I see this appe...

What is the challenge? Currently, there are log events for successful updates made from Jira when using the "Update Records" action What is the impact? Users have no way of knowing which records were successfully updated and what fields were chang...

Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...

I have a JIRA 2.0 integration setup for one of my workspaces. When I push over an Epic containing Features and Requirements, the Features are linked to the Epic but the Requirements are not linked to the Feature. So in JIRA, you can easily see how...

We recently integrated JIRA stories mapped to Aha! requirements but are running into an issue with stories moving from JIRA epic to JIRA epic. Currently, Aha! supports stories moving from epic to epic, but only if those epics are mapped to feature...

When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...

We use the Aha API to populate views in Tableau. The Initiative [API] ID is a crucial portion of making sure what we sync to JIRA from Aha and what we are looking at in Tableau which provides a combined view of both tools, is one and the same. I a...

I would like to be able to set a filter in my Integration for which Jira Issues to sync up. An example would be to not push stories into Aha until there is a point value or time estimate entered in Jira. Another would be to only push to Jira if it...