Hello,
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?
Thanks,
Larry
"Create linked issue" is for creating an issue in the same JIRA system. So it will be able to create issues in the projects in your Cloud system.
It's not for creating remote issues, so it won't touch your Server install.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Nic,
I've chosen to go with an addon to achieve this. It seems to work out ok. Thanks for all your input. I'm also fiddling with script runner.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Which add on did you go with @Larry Barker? Having similar trouble here despite having all permissions for Create and Linked issue set up.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Larry Barker which add on you used?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.