Jira
Sort by:
Trending
Status:
Future consideration
Showing 180
4
VOTE
Support for Jira Expand and other Macros in Aha!
What is the challenge?
Currently, Aha! does not support expandable macros (e.g., collapsible sections) coming from Jira Description.
What is the impact?
This leads to significant data loss — important contextual information, formatting, or...
0
Future consideration
9
VOTE
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...
4
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
207
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
1
VOTE
Pull Integration update on single linked Jira item
What is the challenge?
Need all fields updated from a Jira item, but the only current options are update all from Jira or "Resend all fields".
What is the impact?
Users have to manually go into each field in Jira they want to update, chang...
0
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
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
35
VOTE
8
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
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
© 2024 Aha! Labs Inc.•All rights reserved