Mapping Releases between AHA and JIRA Issues

[Candice Cleaveland]

We have an integration setup between AHA and JIRA. We have the releases in AHA mapped to releases in JIRA, and the integration to setup the fields to cross update between the two when we update either platform. 

Expected Behavior:

- When we update the "Release" field on an epic OR feature (story in JIRA) in AHA, it should update the respective field on these items in JIRA. This does work right now! 

- When we update the "Release" field on an epic OR story (feature in AHA) in JIRA , it should update the respective field on these items in JIRA. This does not work right now! 

The error we are seeing is that it's a naming convention issue, however everything on both sides is accurently named to match both platforms. Any insight on this would be amazing and thanks in advance! 

[Dave Rosenlund _Trundl_]

Hi, @Candice Cleaveland  👋   The $64K question this is going to be how were your Aha! and Jira systems integrated?

Was the Aha! solution for integrating them used? Did your team build something in-house? Was an Atlassian Marketplace app used?

My educated guess is the Aha! integration was used, and therefore your question is best directed to Aha!.

Hope this helps,

-dave

[Dave Rosenlund _Trundl_]

P.S.  Of course, if someone here has already been through this before you, you might get lucky and hear from them here.  😊

[Candice Cleaveland]

Hi Dave! Thanks for your quick response and we ended up discovering that we did map the fields appropriately in AHA to sync both ways BUT we did not sync the Release Name to do so. 

We did start the integration in AHA and unfortunately there are usually decent delays hearing back from their support so I thought to try here as well! 

[Dave Rosenlund _Trundl_]

Glad to hear you got it sorted out, @Candice Cleaveland  😎 

But I am sorry to hear you have troubles getting timely answers from Aha 😕

[Candice Cleaveland]

Thank you! And it's not a problem at all, always worth checking both side of the integration and the AHA team has helped us troubleshoot a number of customization items!