Jira
Sort by:
Trending
Status:
Showing 240
2
VOTE
JIRA and Aha synchronized numbering
We understand that the IDs in AHA and JIRA are meant to be treated as separate IDs without a true association between the two systems. However our workflow allows us to use the same IDs in both systems, assuming we enter them in the same order. Ho...
0
Unlikely to implement
1
VOTE
"Do you want to sync features as well?" (for Jira/Aha integration)
In my organization we need to sync features and releases in Aha to two different Jira projects. One project receives 100% of the features and releases - perfect 1:1 sync. But the other project is only for features that rely on the design team. So ...
3
Unlikely to implement
1
VOTE
Show Integration Errors Next To Integration Link
So often tickets stop syncing between JIRA & Aha! for one reason or another and yes, I understand there is an Integration Updates modal, but when you are working in a ticket, I should get a little error icon next to the link, in the record, if...
0
Future consideration
2
VOTE
Keep unsupported 3rd party Jira tag as it is upon syncing
In Jira, it is possible to render Gherkin by using 3rd party plugin.
After modify the description field in Aha! and synced with Jira, the format is ruined by Aha!.
Original Description on Jira:{code:gherkin} Scenario: The empty state text sh...
0
Future consideration
2
VOTE
Need an option to sync Jira fixVersion "Name" instead of "ID"
Aha! Feature may contain Requirements from different Jira Projects. Right now, the fixVersion is synced with "fixVersion ID", which will not be synced successfully when the Feature (Epic in Jira) and Requirement (Story in Jira) belong to different...
0
Already exists
1
VOTE
Make fixed workflow transition enforcement optional for Jira integratations
Jira is our source of truth for synced items, so if Jira somehow allowed a status change to happen we don't want Aha! to [almost] silently ignore it.
With the current behavior, any discrepancy makes Jira and Aha! grow apart and we really need...
0
Future consideration
1
VOTE
Change Button Click to Dropdown for Integration Screen
When completing the Integration, a user is asked to click through the various buttons showing the direction of the integration. A user has to make several button clicks to change the option, which is not always convenient. A drop down menu would b...
0
Future consideration
1
VOTE
Features assuming the same release as its parent master feature when importing from Jira
Given that I have an epic in Jira, linked to a Master Feature in Aha
And the Master Feature is found in "Release X",
When I create a story beneath that epic in Jira,
Then the story should be imported as a child to the Master Feature,
AND ass...
0
Future consideration
1
VOTE
Working with JIRA worklog dimension (worklog date)
Dear aha, in order to resolve reporting of time spent on features within specific timeframes, it might be useful to think about including worklog date of JIRA issues into synchronized aha backlogs. This would enable creation of reports where not o...
0
Future consideration
2
VOTE
