What is the challenge?
The challenge is restricted to the Aha workspaces tha are integrated with multiple Jira projects.
If the are epics tied to a single release and the epics are pointing to different Jira projects, Aha creates a correspondin...
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
almost 5 years ago
in Jira
3
Future 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
11 months ago
in Jira
1
Future consideration
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
over 6 years ago
in Jira
5
Future consideration
Manual Sending of Requirements to integrated development tool
Presently, there isn't a way to have requirements in a draft status like there are with features. This tends to be somewhat problematic when you have multiple requirements types you work with e.g. subtasks and user stories. It will automatically s...
I R
over 2 years ago
in Jira
2
Future 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
6 months ago
in Integrations / Jira
2
Future consideration
Add an option for JIRA integration to re-import all stories under an epic
What is the challenge?
Sometimes we links epics after they are created. In this case stories aren't linked automatically. That means we need to do an extra step to import the stories
What is the impact?
Error prone and aha doesn't reflect ...
David G
3 months ago
in Jira
0
Future consideration
Synchronize Aha! organizations custom field with Jira Integration
What is the challenge? We heavily use the Organizations custom field in Aha to map customer engagement and roadmap transparency and need that info to sync to our Jira instance. What is the impact? Disconnected systems, duplicate data entry, poor u...
Guest
about 1 year ago
in Jira
2
Future 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
almost 10 years ago
in Jira
17
Future consideration
Epic progress doesn't update when it has children in different projects
Who would benefit? Customer using Jira epics to manage work in multiple projects What impact would it make? They would be able to see their progress in Aha! correctly How should it work? If you have an epic in Project A, and it has multiple childr...
Kyle d'Oliveira
over 1 year ago
in Jira
2
Future consideration