I recently started utilizing Aha! to vet feature requests as well as bugs before sending work to our development team. Aha! is meant to be used primarily for developing features, so I'm working against it a bit by even including bugs in my review. When Aha! submissions are sent to Jira they automatically are assigned "story" as the issue type, assuming that we are dealing only with features.
- Within Aha!, I created a custom field to differentiate Aha! "features" as either a true feature or a bug from my perspective.
- I have a corresponding custom field within Jira that denotes whether the received issue originated as a feature or bug within Aha.
- Using Automation Rules within Jira, I made a simply statement that says the following:
1. When: issue created
2. If: matches 'Aha Type' = Bug
3. Then: Edit 'Issue Type' change to 'Bug'
The rule worked perfectly, and allows me to manipulate the system a bit by forcing Aha feature requests to be changed from a Story to a Bug when the issue is created within Jira.
The problem now, is that the integration between the two systems fails after the automation runs. I have tested changing information on issues that DID NOT use the automation, and I can send/receive from both channels without issue. However, any Aha feature that was sent and also used the Jira automation rule will not update after the initial passing. I make changes in Jira that are not reflected in Aha; I make edits in Aha and attempt to push the "integration updates" to Jira and see two error messages.
"Record in remote system does not exist or you do not have permission to see it."
"An error occurred contacting Jira: Record in remote system does not exist or you do not have permission to see it."
I am a system admin in both systems, I can see the records existing in both systems. Any idea as to why the integration fails after it passes through the automation rule?
Thanks,
David
I am seeing the same issue, no pun intended. In Aha, create Epic, create Feature in Epic. Then Send Epic to Jira -> Feature is also sent as a Jira Spike. What I wanted was to manually send the Feature as a Dev Task instead.
You can't change the Jira issue type once the integration occurs - it breaks the sync. So this is the same poor outcome.
I have to delete the integration link, the change the issue type in Jira, then add the link manually in Aha.
Working with an Aha PS consultant to try and figure this out.
I did change my default Feature name to "Issue" FYI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.