Jira

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

It would be great to have a dedicated integration user instead of having to use a user license for this purpose. I would love to keep my user and the updates from integrations (Jira, TFS,...etc) separate so that it is clear who made the update in ...

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? 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? 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? Once you ignore an integration candidate, it is ignored forever unless you manually import or link the ignored record. If someone ignores a record by mistake there is no recourse to review those potential errors and correct ...

I am able to sync my detailed estimate field in Jira integrations, but not initial estimate.

What is the challenge? When statuses are mapped as bi-directional in integrations (Jira etc.) - transitioning rapidly between statuses in a fixed workflow in Aha! does not send each transition to the dev tool. With a fixed workflow in the dev tool...