Jira

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

Using the Enterprise+ Capacity Planning for Teams feature, you can define an advanced estimate on a feature record and send it to the Jira. The total value of the advanced estimate is correctly reflected in Jira. However when the estimate is updat...

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

What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...

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

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

When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...

When a user creates a Jira integration, the final screen automatically provides a webhook URL. There is an instruction in the help text above that indicates that you may not need to create the webhook, but many users are not aware as to whether a ...

Sometimes we need to investigate synchronisation errors between Aha! and Jira. We can find these errors long after an initial error might have happened. We might need to go back to the original error which may have happened months ago. The limitat...

Some of our fields in Aha are solely dictated by the field in Jira, for example Status. Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrite...