Jira

Currently, when a feature or epic is created in Jira and pulled over to Aha! via the integration webhook, the created by user defaults to the Aha! user who is the webhook "run as" user. Even if there is mapping setup to map the Jira "Reporter" to ...

What is the challenge? The product team manages the roadmap in Aha! and the dev team manages the development in Jira. Stories sometimes slide from one sprint to another and the date range of the release is not up to date with the reality What is t...

Sometimes it is difficult to keep Jira and Aha Requirements up to date when/if a requirement is deleted. I'd like to see a Mapping that is allow to delete and you can select which direction that can occur.

Need to support the Jira code markup option. If the developer enters sample code as part of the description in Jira, the description gets updated in Aha! However the code markup is translated into very large tables in Aha! At some point, Aha! upda...

The following idea is for the JIRA integration, but could describe integrations to other development tools using a similar web hook mechanism. The integration template functionality allows settings from a master template to be adopted by child int...

When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...

Hi All, We are having some trouble keeping an idea's subscribers & watchers in the loop on the idea ticket from its conception through completion. The fact that people can subscribe & watch ideas is great (we find the email updates very he...

Who would benefit? Jira integration users What impact would it make? Currently Jira is sending broken formatting when fields leverage wiki-rendering with tables How should it work? If a user makes an edit to a table in Jira on a wiki-rendered fiel...

The Problem: Jira requires each User Story type to have a Fix Version associated with it, similar to the Epic. The Epic will have Stories with various Fix Version ( the User Stories don’t inherit the Epic Fix Version as story releases are weekly o...

We would like to have a means to integrate Aha! release phases with JIRA sprints, as features included in phases are sent to JIRA.