Jira

What is the challenge? Bi-directional sync of the Jira team field is only supported for some Aha! custom fields What is the impact? Mapping to a predefined choice list is not ideal because it requires us to manually update and map each tea...

What is the challenge? Currently you can add custom initiative fields to record layouts, but these fields are not available to map in the Jira integration. What is the impact? Unable to pass this information over to Jira Describe your ...

What is the challenge? When using an integration template to connect Aha to Jira, the child integrations inherit the Jira project from the original template. This causes authentication issues if the user doesn’t have admin rights to that specifi...

What is the challenge? The challenge is restricted to the Aha workspaces tha are integrated with multiple Jira projects. If the are epics tied to a single release and the epics are pointing to different Jira projects, Aha creates a correspondin...

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? Need all fields updated from a Jira item, but the only current options are update all from Jira or "Resend all fields". What is the impact? Users have to manually go into each field in Jira they want to update, chang...

What is the challenge? We have a shared template across all of our Jira integrations to manage the configuration globally. However, using a global template forces us to have the same integration username (mine, the Aha!/Jira admin) across all pr...

What is the challenge? Currently, scripted fields generated in Jira, even if they are Number fields, can only be imported as Text custom fields in Aha. This means their numerical values cannot be treated as numbers, only as text. What is the...

What is the challenge? Sometimes we links epics after they are created. In this case stories aren't linked automatically. That means we need to do an extra step to import the stories What is the impact? Error prone and aha doesn't reflect ...

What is the challenge? When "Use Jira and overwrite Aha!" is selected, there is a full sync of all fields, allowing fields to update in Jira. But, when "Use Aha! and overwrite Jira" is selected, that same full sync is not performed, and one-way ...