So I have integrated 2 JIRA environments. 1 Cloud, the other on-premise. The JIRA Service Desk cloud environment is able to see the target project in the on-premise JIRA instance when we just want to link an issue to another issue in that environment. However, if we try the 'create linked issue' option we can't see even the target project any longer. I have admin rights in both environments along with create/link issue rights in the target project.
Any ideas as to why we could maybe see it in the first case, but not the 2nd?
Ugh, seriously. Thank you for pointing that out. So you can link to external JIRA systems but not create a ticket. Sigh. Anyone else out there pushing tickets from a JIRA ServiceDesk to a segregated 3rd line bug tracking instance?
Years ago we pushed from Salesforce cases to JIRA, and most recently from our Zendesk environment to JIRA. If JIRA can't even push a ticket to another JIRA instance, I'm going to have to rethink migrating away from Zendesk.
That is just the issue linking - JIRA needs an issue object at both ends of a link, which you can't do because the remote thing won't be an issue object.
But, yes, we do exactly what you describe in more than one place.
The basic set up we use is:
That third step is roughly the same as what your Salesforce and Zendesk things are doing.
Just the FAQs! Welcome to the Community, and this Focused-FAQ! Here, we've pulled together some of the most frequently asked questions associated with Jira Service Desk (JSD). We hope ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs