At creation time of issues using the bulk csv import method, is there a way to link two issues as *relates to? If so, can you please provide me with an example?
Hi @rfrazier1 ,
I've just tested this and it seems it's possible.
You could use something like this (I haven't actually used "Parent ID", so it can be removed):
During the import, you could then select link type (e.g., "Relates").
⚠️ When using bulk create via CSV, you need to have appropriate global permission and also all fields you'd like to import would need to be on create screen. In your case, you would need to have Linked Issues (yeah, they still didn't rename that to 'items'...) field on create screen to have a successful import. 👈
This will/should work from import option you're accessing (so, you do not need to use Jira admin external import).
You can see this reply/thread for additional insights.
Anyway, this is what the result based on that CSV screenshot at the beginning looks like.So, you could link an existing item, or an item that is also created via CSV import (a non-existent one). It should work in both cases.
Hope this helps.
Cheers,Tobi
Hello @rfrazier1
Welcome to the Atlassian community.
For clarity can you tell use exactly how you are accessing the Bulk CSV Import feature? There are multiple ways to access the feature depending on your level of access. Knowing which method you are using will enable us to advise you more effectively.
Hello @rfrazier1 ,Welcome to the Community!You may link via the External system - CSV import !!I would suggest you may use API call using postman or script
I am accessing it through the Project page - the three dots. I believe I have minimal access in Jira. I'm trying to link a story spike and story as relating to each other upon creation using the bulk csv function.
Do you have a link for this documentation?
The External System Import mentioned by @Piyush Annadate _ACE Pune_ is available only to Jira Administrators. If you click the gear icon near your avatar in the upper right corner and see an option for "System", then you are a Jira Administrator.
Can you provide a screen image showing the Project Page where you are finding the option?
Thank you @Tomislav Tobijas Is it safe to assume the 'relates to' will not work at bulk update time if the fields do not exist at creation time? For example, a story spike and a story have already been added, but I want to go back and update these two to relate to one another. Since these fields exist in the database, it seems I should be able to add them at creation or at update time in the bulk csv.
@rfrazier1 for bulk update (via CSV) you'll need to use Jira admin interface (Settings > System > External system import). Check out more here > scroll just above the linked section.
Now, as this can be done only via Jira admin nav/page within which you can use all fields, linked issues don't necessarily need to be added to the screen. Work item linking, of course, needs to be enabled.
It's not really that straightforward, but as stated here, you can check on which 'import experience' you're currently at:
Now, to actually bulk update items via CSV, it would seem you'll need to be Jira admin and navigate to Settings > System > External system import and from there, once you get to mapping window, URL will look something like this: https://<sitename>.atlassian.net/secure/admin/CsvFieldMappingsPage and in there, you'll be able to select pretty much any field, including the one for Work item key. (in order to make bulk update via CSV)
@Tomislav Tobijas
The author indicated in their response to my answer that they do not have administrator access, so they will not be able to access the External System Import function.
It looks like you're new here. Sign in or register to get started.
