Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

I am importing an Issue using a JSON file, but I want to set an Organization to the Issue.

caio
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 10, 2019

I am importing an Issue using a JSON file, but I want to set an Organization to the Issue.

Where is the documentation page about this?

Until now I only found some examples, but nothing about the Organization field.

2 answers

0 votes
Bart Seresia
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 8, 2023

As I landed on this post while looking for a sollution for the same problem I thought it might be good to share an other post i found that actually worked : https://community.atlassian.com/t5/Jira-Service-Management/What-is-the-JSON-format-to-import-field-cf-11900-a-k-a/qaq-p/1250510?anon_like=1278879

In short, use the custom fields, use the field id as name and the organisation id (not the name) in the json.

Works like a sharm

0 votes
Tim Prentis December 12, 2019

RE: 'Organizations' and Data Migration for Jira Service Desk Cloud (In my case migrating 2 systems (ZenDesk and OSTicket) to Jira Service Desk.

I have the same issue with importing issues and setting the organizations multiuserpicker field (i.e. in my case customfield_11900 or cf[11900]).

The only way I have been able to set this field value is to create the organization for Jira Service Desk Project and create a different custom field to store the 'legacy organization' name in for the issue.  I populated the 'legacy organization' textfield in the import JSON file with the 'legacy organization' name and executed the 'External System Import' creating the migrated issues.  BTW, you might find it helpful to create 'legacy' fields for a few of the fields you may need from the old legacy system and include these fields in you JSON import file. (i.e. Legacy_Organization_Name,Legacy_Ticket_Number,Legacy_Ticket_Reporter, etc.)

After I imported the JSON file successfully, I then used JQL to find the tickets for each organization (In my case I had 2 orgs).  Something like this -> Project = ProjectName AND "Legacy System Name" ~ OrganizationName

The JQL limits your issues to the Organization you want to update (Note: it will only let you edit 1000 issues at a time so you may need to do this a few times. And you should change your JQL to filter the records you just updated. (i.e. Project = ProjectName AND "Legacy System Name" ~ OrganizationName AND cf[11900] = OrganizationName). Note cf[11900] is the internal name for you 'Organizations' field. You will see this when you start keying the word 'Org.......' in your JQL where I am showing cf[11900]. Trust me, although your internal field name may be something other than cf[11900]. You'll just have to play around with this)

 

Now, select the 'BULK CHANGE' feature (on my page it is located in the upper right corner behind the '...' (three dots))  and then select The issues you want to update (Generally, All Issues). Then choose 'operation'  Edit Issues' which will present a page of the fields defined in the project. SCROLL DOWN and find the first 'Change Organizations' field (there may be multiple 'Change Organizations' fields, depending on the number of Organizations you have added to the system)

Then key in the 'Oranization Name', (which should pop up in a list presented below the field when you key the first letter of the Org Name.)

Now scroll to the bottom of the page and find the checkbox labelled 'Send mail for this update'. Check or Uncheck this checkbox before selecting Next.

After selecting Next you will get the 'Confirmation' pageThe rest of the process is fairly evident.

Apologies for the diatribe, but this was my solution/work-around, due to lack of JSD documentation for setting this 'organizations' field value in the JSON import file  

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events