JIRA Bulk Upload

[Greg Gibble]

Hello,

I have been given the role of taking over creating and managing our JIRA boards. The process that was set up works fine, except for one small fact, when I bulk create issues using the CSV loader, all of the tasks get assigned to me when I would want to get them assigned to the relative project managers coming to me. Where in my CSV loader should I be looking at to fix this?

Thanks

[Alexander Kravchuk]

Hi @Greg Gibble 

As Mikael said, you need to map your "Assignee" field on the configuration to correctly import. You also mentioned "tags", which I assume are "labels" in Jira language -- you can leverage them after the fact: either by filtering issues by certain label and running bulk assignee update or create an automation rule, which is triggered by "Issue Created" event and if it matches certain conditions (such as "label == project_manager") you edit Assignee field and set it to a certain person.

[Greg Gibble]

Okay this would be interesting to me so I wouldnt have to change my current process that is set up. Each time I bulk create they all will be assigned to a specific component. 

Can I create a bulk assignee update off of that? If so do you possibly have any examples or know where I could find one. 

Thanks ahead of time.

[Alexander Kravchuk]

I don't think you can create automatic bulk updates, but as I said - you can create an automation that is going to be triggered on the creation of each issue (which effectively the same as bulk update as it is going to be triggered for each issue anyway) or scheduled automation that is going to do the same. But depending on the amount of issues you import, you need to take into account automation service limits.

[Mikael Sandberg]

Hi @Greg Gibble,

Welcome to Atlassian Community!

You need a column in your csv file for the assignee reporter (their email address), and then add that to your mapping configuration in order to set the assignee to someone else then you.

[Greg Gibble]

@Mikael Sandberg  So currently I dont have my address in there and it is still assigning it to me.

There are tags such as project_manager and program_lead in the csv file. I want to make sure i can have this as an automated process so I dont have to update the file each time. 

Are these tags grabbing the users there or somewhere else?

[Mikael Sandberg]

If you do not map a column in your csv file to the assignee field, Jira will automatically set the reporter to the person running the import. What is being imported is controlled by the mapping configuration.

[Greg Gibble]

That makes sense. So is there no way for me to dynamically pull this information in other then inserting the emails into the import for the assignee each time?

[Mikael Sandberg]

Correct, the only way to get the information is to have it in your csv file.

[Greg Gibble]

Thank you for your knowledge here!

[Greg Gibble]

Hey sorry, it is actually the reporter field being populated with myself, the Assignee field is set to unassigned. So then I am guessing somewhere in my csv the assignee field is being set? 

I dont even mind if this field is set to unassigned as well, I just dont need to be getting notifications for everytime someone updates a ticket

[Mikael Sandberg]

My brain was on auto-pilot this morning. You are correct, it is the reporter that will be set to the user running the import unless you have a column for it in the csv and map it to the reporter in the configuration.

[Greg Gibble]

This is part of what I was trying to add into the uploader, i ran my process and it created the tasks with no issues but still had myself as the reporter. Am I on the right path here then?

Note: in my run I used an actual email not the example_email.

[Mikael Sandberg]

Does your mapping have an entry for the reporter?

[Greg Gibble]

I believe so with the picture i just sent. Is that not the correct way to map it?

[Mikael Sandberg]

The picture only shows the headers from the csv file. When you do the import you will be asked to map these headers to a corresponding Jira field. Make sure that you are mapping a header to the reporter, if that is not done Jira will default back to set the reporter to the user running the import.