Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
Guest
over 3 years ago
in Jira
1
Future consideration
Including Dependencies in Jira integration at requirements/story level
We have been really enjoying the newer ability to include dependencies for features in our Aha-Jira integration, but are running into the issue not getting the same level of transparency for the user stories - to combat this, we would like the abi...
Trey S
almost 4 years ago
in Jira
0
Future consideration
Show comments added in JIRA as part of a state transition.
Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA.
This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This means...
Michael Buonassisi
over 6 years ago
in Jira
2
Future consideration
The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
Wen-Wen Lin
over 6 years ago
in Jira
0
Future consideration
Allow auto-import of JIRA issue without the need for a "parent record" (or just a pre-defined default like with manual import)
I was a bit confused when I could import items from JIRA manually, and webhooks were working both way, but when I made a new issue in JIRA, it was not getting auto-imported. I read through lots of really long explanations about the need for "paren...
Guest
over 8 years ago
in Jira
3
Unlikely to implement
What is the challenge?
Currently, Aha! does not support expandable macros (e.g., collapsible sections) coming from Jira Description.
What is the impact?
This leads to significant data loss — important contextual information, formatting, or...
What is the challenge? The Jira integration does not currently support the table markdown syntax What is the impact? The result is a formatting issues when a record including a table within the description is synced to Aha! via the integration Des...
Terri Salie
about 1 year ago
in Jira
1
Future consideration
What is the challenge? Unable to Sync deleted and edited comments between Jira and Aha! What is the impact? Syncing deleted and edited comments between Jira and Aha! is crucial to maintaining accurate and up-to-date communication across teams. If ...
Prachi H
about 1 year ago
in Integrations / Jira
1
Future consideration
Allow for parent-child linking across Jira projects without using an integration template
Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush
over 2 years ago
in Jira
0
Future consideration