Integrations

In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...

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

My team has switched from Fogbugz to Linear for ticket tracking. We'd like a two-way sync between Aha features and Linear Issues.

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

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

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

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

What is the challenge? Many organizations use OKRs for their strategic planning. They need a way to measure how their resulting deliverables measure against the originating KPIs. Many telemetry tools such as Grafana and ClickHouse monitor this ...

link/create conversation to idea

What is the challenge? The release field is available in the Jira integration under the Aha! feature/epic record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the release as a s...