We are dealing with 2 Jira instances. The "original" instance tracks software development. It is the one we first heard about and are currently working with. We were just told of a second instance which tracks software review board work. The reviews pertain to the sw development done in the 1st/original instance.
We had created a new Jira Server instance, created a project and are now importing .csv outputs from the original instance. Regarding the new second instance, we were thinking to just do the same thing we did for the original instance however - crete a new project and import the work.
Now there is a requiremen to link the isues from each project, where appropriate.
The problem is how to do this? I don't see a single point of reference between either the original or the second Jira instance. The Keys and IDs are totally different and I just don't see how this can be pulled off.
Any ideas?
Thank You,
Jim
Hello @James Malgieri
Thank you for reaching out.
Per your description, I understand you are struggling to identify a common field to properly check which issues should be linked to another in two different instances. Is that correct?
Indeed, there is no way to know what issues should be linked to another if there are no fields that provide this information, however, since you mentioned that the issues of the second instance are created to review the development done in the first instance, can you check if there any text field in the issues of the second instance (reviewing) containing the issue key or summary of the first instance issues (Development)?
If there's, you could simply search (Command + F) the CSV file from the development instance with the related content and link it directly in the CSV, as described in the documentation below:
Import issue links from a CSV File in Jira server
These would be the exact steps:
Let us know if you have any questions.
Petter,
Thank you very much for your help. I'll do what you suggest and if I run into any problems will get back in touch.
Thanks Again,
Jim
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.