Set custom workflow as default -JIRA 5.2

JIRA 5.2

I've created a custom workflow and would like to set it as default so that when I use CSV import the custom workflow will be applied instead of jira(system workflow)

Whenever I import issues via CSV import the system workflow(jira) is used

Thanks

5 answers

1 accepted

I think it's not possible to change the defult workflow for the projects created during immporting CSV. Anyway, you can always change it after the importing done via the project configration.

Have you have created the custom workflow first before starting CSV import?

If not, then create one and associate it to the workflow scheme and finally associate this workflow scheme to the project in which you want to import these issues via CSV.

Hope this helps!

Hi Naren,

Thanks for your reply!

Yes I have created the workflow before CSV import, But the problem is the projects are created by the csv import itself and none of the projects currently exist.

Is there any way to associate the csv data to a workflow? OR set the custom workflow as default.

As Amanda said, you can create custom workflows and associate the same to a Workflow scheme. And during the CSV import process, in project configuration step, you can select the workflow scheme you created.

This way the projects getting imported will be associated with these workflow scheme. Then you can map the statuses in the CSV file to the statuses in the custom workflow you created.

This can solve your problem!

Amanda,

Thanks for confirming, but this doesn't help because the csv import is failing due to the mapping of custom workflow statuses. and some issues doesn't get imported (failed with following error)

Error importing issue ExternalIssue{externalId=autoid-1124514781001314797, summary=null, issueType=null}

You'll need to create the projects and associate them with the correct workflow schemes BEFORE importing the issues.

As the error states, the summary and issuetype should not be null for the issues you're trying to import from CSV file.

Try adding the summary and issuetype values to such issues in the CSV file.

As the error states, the summary and issuetype should not be null for the issues you're trying to import from CSV file.

Try adding the summary and issuetype values to such issues in the CSV file.

Nic,

Understood now..I'm going to import the projects first and then assign the workflow scheme > import issues. Hope this goes well.

@Naren,

I don't think that's a problem because the same file imports successfully if I use a staus from the default workflow(jira)

Thanks

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,301 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot