Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Jira

Allow aggregating multiple Jira stories into a single Aha! requirement (summary sync option)

What is the challenge? The Aha!–Jira integration requires a 1:1 sync between Jira stories and Aha! requirements. For teams managing large epics, this creates excessive noise in Aha! and makes it difficult to maintain clean, high-level views for po...
Katie Tokarz 9 days ago in Jira Future consideration
228 VOTE

Dedicated Integration User

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 ...
Guest over 9 years ago in Integrations / Jira Future consideration

improve integration between Jira > Aha!

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...
Guest 3 months ago in Jira Future consideration

The ability to review previously ignored integration candidates and undo the ignore

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 ...
Stephanie Lechner over 1 year ago in Jira Future consideration

Sync initial estimate field in integrations

I am able to sync my detailed estimate field in Jira integrations, but not initial estimate.
Alina Mavis over 3 years ago in Jira Future consideration

Jira integration - Allow Jira account username/password modification per workspace when using a shared integration template

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...
CJ Jacobs 11 months ago in Jira Future consideration

Improve syncing fixed workflows with integrations

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...
Jeanette Resnikoff over 1 year ago in Jira Future consideration

Moving integrated Jira records to a new project should update the Jira link and key in Aha!

What is the challenge? When following the guidance in this help article to move Jira records between Jira projects with Jira, https://support.aha.io/aha-roadmaps/integrations/integration-guides/move-records-with-jira-or-rally~7444656710918981281#p...
Terence Osmeña over 1 year ago in Integrations / Jira Future consideration

Jira Integration of custom calculated field

We have a Jira project that supports multiple engineering teams. Each team has their own release schedule. We need a way populate fixversions in jira with team specific values. The creation of a custom field that combines "product prefix-release n...
Russell Roach almost 6 years ago in Jira Future consideration

Add configuration of Jira Integration Alerts to a template

What is the challenge? We have defined a 'Vanilla' template which has been rolled out to all of our workspaces but the ability to configure Integration alert notification recipients does not get picked up by the template What is the impact? We ha...
Sophie Ramsden about 1 month ago in Jira Future consideration