Importing "Unassgined" Issues From CSV

Alex Basile April 22, 2021

Is there a way to Bulk Upload issues from a CSV where the Assignee is "Unassigned"?

If this field is left blank, then the assignee is "Automatic" and the issue will be assigned to someone based on automation rules.

However, I'm looking for a way to upload issues to the backlog so that they are not assigned to anyone until sprint planning occurs.

Thanks!

3 answers

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 22, 2021

What about deactivating your Automation rules while you are executing the import?

What is triggering the automation that is causing the assignee to be set?

Alex Basile April 22, 2021

I've got an automation rule in the project on which I'm an admin that prevents this from happening, but I don't have control over other project automation rules. Can't turn them on/off or modify :/

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 22, 2021

I'm unclear about the intent of the automation.

If it is appropriate for the issues to be unassigned, then why is the automation configured in such a way that it is automatically setting the Assignee for issues in the backlog?

If the intent of the automation is to set the Assignee always, even for new issues added to the backlog, then why are you trying to circumvent that?

Alex Basile April 22, 2021

On the project that I'm having the issue with, there are some issues that are meant to be assigned to specific users and others that should be left "Unassigned".

The automation rule is in place to make sure that the reporter either chooses a specific user or specifically marks the issue as "Unassigned", rather than ignoring the "assignee" field altogether.

If the field is ignored (left in "Automatic"), then the issue gets assigned to the project admin, then they receive a notification and follow up with the reporter to see where the issue is supposed to go.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 22, 2021

Ok, now I understand.

Looking at this issue

https://jira.atlassian.com/browse/JRACLOUD-71877

...it seems like you should be able to specify "unassigned" as the Assignee in the CSV file, and if you use the import functionality available to JIRA Administrators then it should work.

If you are not a JIRA Administrator, then it appears there is no way to force it to be Unassigned in your case, with the automation rule running.

Alex Basile April 22, 2021

I'm a Project Admin, not a Jira Admin, so my importer is slightly different. The importer won't pass any non-numeric values through that field (it has to be a user id or the issue will bounce).

Sounds like I need to talk to the other Project Admin about their automation rules!

Thanks : )

0 votes
resfulany
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!
October 31, 2022

Try this: _unassigned_

Daniella Eguiguren April 19, 2024

This did not work for me, unfortunately. Upon validating the import (before creating), I got this error: "Issue can't be created due to the error/s [ User '_unassigned_' does not exist. ]"

0 votes
S Fong December 31, 2021

I found the same issue which I want to leave the assignee [blank] but it went to me instead after I upload the CSV file.  I don't have any automation rule created for this and I believe that it is default from Atlassian.  Does anyone know a way to bypass it so I can upload with [blank] assignee?

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 31, 2021

Hello @S Fong 

Are you using the import available to Jira Administrators (through Settings > System > External System Import) or the import available on the Search Issues screen?

Refer to this issue: https://jira.atlassian.com/browse/JRACLOUD-71877

It seems that if you are using the import through the Search Issue page, you cannot import the issues with no Assignee.

You would need to have a Jira Administrator import the issues through External System Import, it appears.

Like S Fong likes this
S Fong January 4, 2022

I am a Jira Administrator and use CSV import via Advanced Search Issue screen.  So if I use External System Import, then I can have [blank] assignee mapped?  Thanks for the insight.  

Nagyné Széles January 10, 2022

Exactly the same situation here, as admin, importing from csv through the External Sytem import from admin (and not the issues page import from a project). I tried "unassigned" as reporter, but it still puts the reporter on me. 

Like S Fong likes this
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 12, 2022

@Nagyné Széles 

You have mentioned two different things - Assignee and Reporter.

This thread is about ensuring that the Assignee field is set to Unassigned, not about the Reporter field.

Please clarify your issue. If your issue is indeed about the Assignee field, please let us know if you have any Automation Rules that are filling in the Assignee field automatically for newly created issues. Check the history on the issues to see the data on when the Assignee field got set and by whom.

If your issue is about the Reporter field, then be advised that the Reporter field is not allowed to be blank. If you don't explicitly specify a Reporter in your import data, then the Reporter will be set to the person executing the Import process.

Nagyné Széles January 17, 2022

Yes, thank you, I realised in the meantime, that reporter can not be blank, I confused it with the unassigned, it should be unreported lol, thank you for you answer anyway, I made my peace with the fact that all imported tasks will be reported by me in our new Jira :) Have a lovely day!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events