Our Jira environment has a requirement to enter a comment when "closing" a ticket. Aha does not have a place for this so if Aha! users close a feature in Aha, they will have to login to Jira and close it there as well. The request is to allow a "c...
Guest
about 3 years ago
in Jira
0
Future consideration
Allow integration of Custom Fields to any Jira Field of a supported field type
We have a process where we track issues reported by Release. Our issues come via Cases in Salesforce, which are then pushed as an Feature in Aha which captures the Affected Version in a custom field.
We would like to push this custom field valu...
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...
Guest
over 6 years ago
in Jira
0
Unlikely to implement
"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 ...
Byrne Reese
over 3 years ago
in Jira
3
Unlikely to implement
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...
Guest
over 3 years ago
in Jira
0
Future consideration
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...
Guest
about 7 years ago
in Jira
0
Future consideration
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...
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...
Daniel Hirschberg
almost 4 years ago
in Jira
0
Future consideration
On some occasions we will end up with multiple JIRA tickets for the same item in AHA. We'd like to be able to track each of these in Aha, but most importantly be able to pull the time tracking data into aha across all of the tickets.
Guest
over 7 years ago
in Jira
2
Unlikely to implement
Useful to keep users of JIRA and Aha in sync between systems without managing Watchers across installations.
I've noticed that @ mentions in Aha! do not match the JIRA username on comments. I want to ensure that JIRA users are notified when I @ m...
Ryan Schultz
over 7 years ago
in Jira
0
Unlikely to implement