Jira

When adjusting settings that are referenced in an integration, there is no warning that integrations will be impacted and users are not guided to update their integration settings. There are two main settings that result in notable issues in the i...

It's helpful for the scrum teams to not only see the Aha rank but also the business value associated with the scorecard. Integrating scorecard with JIRA Business Value is beneficial to members of the teams as well as reporting on the business valu...

Who would benefit? Anyone using Jira integrations What impact would it make? "Parent Link" and "Epic Link" fields have been replaced by a new "Parent" field in Jira. By recognizing this new field, integrations will not break and can use the new fu...

When sending or linking a Aha feature to a Jira Epic the system uses the name of the person who created the Jira integration record instead of the user who created the epic. This results that all Jira issues now show up as Reported By with the nam...

Up until recently, custom field data was sent one-way Aha to Jira. For certain fields, we prefer the data sent one-way. We want to be able to send information such as business goals so that people using Jira can understand more about what's trying...

Each of our workspaces is integrated with Jira, but often our POs question why things are missing and feel that the two applications are not always kept in sync properly despite having both the incoming and ongoing changes set to 'approve automati...

As a product manager with an engineering team that uses Jira, I understand and appreciate that Aha aims to remove the temptation for anyone to "sneak" tasks into Jira rather than through the PM and Aha!. The reality, though, is that agile sprints ...

We have a large organization with ~400 projects in JIRA, where 1 JIRA project = 1 agile team. We would like to sync all teams' epics with Aha, but the current UI only allows creating integrations 1 product at a time. Assuming 1 Aha product = 1 JIR...

If you have an environment where the engineers are not setup in Aha!, what ends up happening for when you have Features/Requirements linked to JIRA Issues is when assignments are made in JIRA, the assignee information that is synced back to Aha! d...

Like many other users, we map features to tasks and requirements as sub-tasks in our integration. For us it logically makes sense that JIRA Epics are therefore bound to releases (as tasks sit under Epics, and features sit under releases) - we use ...