Within the JIRA integration, add the ability to hide options to 'send to' JIRA and only show the 'link with existing' options. This would be helpful for integrations that are designed/configured to be only 1 way (JIRA to Aha).
Kyle Kinder
8 months ago
in Jira
1
Future consideration
Please enable the ability to sync a release phase to an Epic in Jira. And also sync release phase To-Dos to tasks in Jira. Use Case: I have a release template with my release phase and associated to-dos. These to-dos are what govern my Jira tasks....
Guest
over 3 years ago
in Jira
0
Future consideration
Persistent filters for integrations and incoming product updates
Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
Guest
over 5 years ago
in Jira
0
Future consideration
Show comments added in JIRA as part of a state transition.
Currently, when a comment is add to a JIRA issue as part of a state transition, the comment is not shown in AHA.
This is a real issue for us since the Engineering team adds useful comments in JIRA when they move an issue between states. This mean...
Michael Buonassisi
almost 5 years ago
in Jira
2
Future consideration
The Product Name contains an import department work categorization that we would already use to filter reports in Aha and would like to be able to do the same in JIRA. There is a similar request to have Product Name in the Slack integration. I won...
Wen-Wen Lin
almost 5 years ago
in Jira
0
Future consideration
When integrating AHA / Jira the field mapping only shows fields that can be editable. We are looking to bring in Created Date and Resolved Date on both the Jira epic and Jira story. These fields are dynamically created and populated based on the f...
Roger Octobre
over 3 years ago
in Jira
0
Future consideration
Please Add a Setting to Turn Off the Automatic Imports of Unlinked Jira User Stories
I believe that the way integration is currently implemented is based on a faulty assumption, e.g. that customers want all user stories created in an integrated Jira project and board to be sync'd to Aha!.
We'd much prefer that this not be the ...
Doug Wilson
about 4 years ago
in Jira
1
Future consideration
Ability to update a file attachment of a feature and update in the linked record of JIRA as well
Hi - We have Aha! - Jira integration where our features are mapped to JIRA stories. Features also have several file attachments which get propagated to JIRA stories. However, our Product Managers need to update the file attachments. Currently ther...
Michael Zadda
over 6 years ago
in Jira
1
Future consideration
Sync story points to Jira without Capacity Planning
My teams doesn't use capacity planning, as we have the same team members each week, but we'd like to be able to automatically link story points to Jira.
Currently this is only accomplishable when you have enabled capacity planning, which causes m...
Michael Clinton
almost 8 years ago
in Jira
1
Future consideration
Integrate Master Features and related features to different JIRA projects
In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...
Guest
over 4 years ago
in Jira
1
Future consideration