Jira
Sort by:
Filter by:
Status
Showing 269 of 9371
3
VOTE
When linking an Aha! record to an existing Jira record, perform a full sync of all fields
What is the challenge?
When "Use Jira and overwrite Aha!" is selected, there is a full sync of all fields, allowing fields to update in Jira. But, when "Use Aha! and overwrite Jira" is selected, that same full sync is not performed, and one-way ...
0
Future consideration
12
VOTE
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...
2
Future consideration
17
VOTE
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 ...
4
Future consideration
199
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 ...
16
Future consideration
34
VOTE
1
VOTE
Ability to import JIRA labels to Aha Requirement Tags
What is the challenge? Unable to import JIRA labels to Aha Requirement Tags What is the impact? DSG tracks in JIRA Stories which business silo owns the work with Tags and tags if the work is carry over from a previous springs. DSG needs those tags...
0
Future consideration
7
VOTE
Add 'Send to integration' automation action for Aha! Ideas <> Jira integration
What is the challenge? As PMs review ideas submitted to Aha! there may be ideas that need to be sent directly to Jira — thinking about bugs that are reported through an ideas portal. What is the impact? Those ideas need to be reviewed alongside al...
0
Future consideration
1
VOTE
Sync Aha! feature date range to Jira associated sprint date range
What is the challenge? The product team manages the roadmap in Aha! and the dev team manages the development in Jira. Stories sometimes slide from one sprint to another and the date range of the release is not up to date with the reality What is t...
0
Future consideration
57
VOTE
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...
3
Future consideration
7
VOTE
Features and Epics should move to integrated parent Release upon updates
What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
0
Planning to implement
© 2025 Aha! Labs Inc.•All rights reserved