Jira

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

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

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

What is the challenge? When users use the "Update Records" action in the Jira integrations, sync failures are logged as Sync errors without mentioning which record failed to update What is the impact? Users are not able to troubleshoot and address...

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

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

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

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

We are getting ready to share Aha with key stakeholders around the company, and we do not want to share the inside engineering chatter with the rest of the company. We have comments in JIRA that should not be broadly available. I would like to be ...