Maintain integration links when Jira records move projects/boards AND sprints are mapped
What is the challenge?
Today, the Jira integration supports movement of integrated records across Jira projects via use of an integration template. However, if the integration includes sprint mapping, a board must be selected in the template. Th...
Brittany Rhoney
23 days ago
in Jira
2
Likely to implement
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! ...
Shiv Shankar Vedharajan
about 1 month ago
in Ideas / Jira
0
Future consideration
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
about 9 years ago
in Integrations / Jira
17
Future consideration
What is the challenge?
Integration links can be lost for a variety of reasons. For organizations with a large number of records, it is not realistic to manually relink or reimport their backlog when this happens.
What is the impact?
Suppor...
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
8 months ago
in Jira
4
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
4
Future consideration
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
about 1 year ago
in Jira
2
Future consideration
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
over 5 years ago
in Jira
3
Future consideration
Ability to map editable choice lists in Aha! with the Jira Team field and support bi-directional sync
What is the challenge?
Bi-directional sync of the Jira team field is only supported for some Aha! custom fields
What is the impact?
Mapping to a predefined choice list is not ideal because it requires us to manually update and map each tea...
Deepti Pradeep
5 months ago
in Jira
1
Future consideration