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 JiraFuture 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
6 months ago
in JiraFuture consideration
What is the challenge?
When integrations are out of sync with AHA and JIRA where JIRA holds the source information.
(1) Delete records in Aha and re-import. This creates issues for any integrations that were set-up in Aha
(2) Use Update Records...
Allow the Release to have bidirectional sync with Jira
What is the challenge?
Today Aha only allows to send the Release field from Aha to Jira, while we have technical teams that use only Jira (developers) and update the release there, while it can't sync back to Aha.
What is the impact?
Incon...
michal regev
3 months ago
in JiraFuture consideration
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...
Complete Auto Import Functionality -- not just children of existing linked records
This is regarding the JIRA integration feature:
Automatically Import New Records:
Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, master...
Guest
about 7 years ago
in JiraFuture consideration
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer
over 10 years ago
in JiraFuture consideration
Ability to update Jira Affects Versions field from Aha via integration
What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...
Kevin Scribner
over 1 year ago
in JiraFuture consideration
Moving integrated Jira records to a new project should update the Jira link and key in Aha!
What is the challenge? When following the guidance in this help article to move Jira records between Jira projects with Jira, https://support.aha.io/aha-roadmaps/integrations/integration-guides/move-records-with-jira-or-rally~7444656710918981281#p...
Terence Osmeña
about 1 year ago
in Integrations / JiraFuture consideration