My ideas: 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...

We want to automate the documentation of all of our integration points (integration to Jira). We would like to see not only the integration name, rather we would like to see the specifics field mapping information , direction of integration etc...

What is the challenge? Aha! webhooks can currently be triggered only by changes to a set of standard fields (name, description, status, assigned user, dates, etc.). Many teams rely heavily on tags, record links but changes to these fields cannot...

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? Dates added on AHA/ADO are not properly synced and show up on the other tool as +/- 1 day as a result of time differences between the two tools. Expected behaviour: When selecting a date in one tool, the same date appears in...

I know that Aha includes the ability to attach documents at the Product Level. However, at my company, we want to maintain Policies & Procedures, but take advantage of the version control available in SharePoint. We want to link or integrate a...

What is the challenge? To export a report to PowerBI, the workspace selected in the top left must be one where the user has contributor or owner permission, even though the workspace selected there does not have any impact on the report being view...

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

It's possible to send the Aha! URL to a Jira field, but most Jira users don't have access to Aha! so it would be beneficial to have the option to send the ideas portal link for the idea instead so that it can be easily accessed from Jira.

What is the challenge? Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies. What is the impact? Epics and features are misa...