Jira

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

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

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

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

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

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