Jira

What is the challenge? When you integrate a parent item like an Aha! feature with a Jira epic the child items of the Jira epic are not automatically integrated as tickets on the Aha! feature. This means you need to do a separate import of chil...

What is the challenge? At present you can only select all fields from either Jira or Aha! as the source of truth for integrating an initiative/feature/ticket to Jira. This presents problems when you have good content on both sides and you want...

What is the challenge? Today, the Jira integration supports movement of integrated records across Jira projects via use of an integration template. However, if the integration includes sprint mapping, a board must be selected in the template. Th...

What is the challenge? We have Aha! and Jira in the mix. teams use Jira smart checklists and Aha ! to dos. It will be beneficial to have bidirectional sync between the two. What is the impact? Teams have to manually sync and maintain Aha! ...

What is the challenge? Today Aha only allows to send the Release field from Aha to Jira, while we have technical teams that use only Jira (developers) and update the release there, while it can't sync back to Aha. What is the impact? Incon...

What is the challenge? Currently, where a Jira Board is set on an integration it cannot be edited or removed. What is the impact? Customers who are not mapping the Jira Sprint field do not need to select a Jira Board. However, once the Boa...

What is the challenge? When integrations are out of sync with AHA and JIRA where JIRA holds the source information. (1) Delete records in Aha and re-import. This creates issues for any integrations that were set-up in Aha (2) Use Update Records...

What is the challenge? Integration links can be lost for a variety of reasons. For organizations with a large number of records, it is not realistic to manually relink or reimport their backlog when this happens. What is the impact? Suppor...

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