Jira
Sort by:
Trending
Status:
Future consideration
Showing 249
118
VOTE
1
VOTE
Synchronize Aha Organizations with Jira Integration
What is the challenge? We heavily use the Organizations 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 user and...
0
Future consideration
148
VOTE
Sync record's workspace, goal, initiative, epic, and release (name and link) to Jira
The use case is so that those working primarily in JIRA can understand “why” they are being asked to deliver “what” has been requested.
In the screenshot attached, it shows a section of the JIRA issue interface. It then shows a tab created specifi...
8
Future consideration
164
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
5
VOTE
Epics that aren't selected for import in the Import list should be saved or maintained in Aha for later import.
What is the challenge? Once an epic is ignored on the import list in Aha it cannot be retrieved to be imported at a later date. What is the impact? Doubles the work of having to create the corresponding feature for the epic in Aha and then link it...
0
Future consideration
1
VOTE
Automatically Update Records Converted in Jira
What is the challenge? Often times our Engineering counters in will convert stories/Spikes/Tasks to Epics in Jira What is the impact? We're not always told when these conversions happen and often have to do duplicate work to go into Aha! and conve...
0
Future consideration
21
VOTE
56
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
1
VOTE
Don't Allow Jira Integration to Fail Based on One Field
What is the challenge? I have a Jira integration that integrates many standard and custom fields. If there is an issue with one of those fields for whatever reason, the entire integration fails and will continue to do so even if there is nothing w...
0
Future consideration
15
VOTE
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...
2
Future consideration