How to import workflow with project

[Vasil Galinovsky]

Hi, I am trying import a new project with json with custom workflow. Workflow was already created in system. How can I set needed workflow in json?

[Nic Brough -Adaptavist-]

What do you mean by "set workflow"?  You've said you have the workflow in there already, so all you need to do is set the workflow scheme for the project.

[Vasil Galinovsky]

I want to create a project from a scratch by import but I can't import some of my statuses because in default JIRA workflow there is no such statuses, In this case I need to create the project first manually and only after that I can import data. I would like to set workflow in json to skip manual steps

[Nic Brough -Adaptavist-]

You'll need to add the status before you can use them in your workflows.  I don't think there's an importer function for that yet, but if you are using the editor to create workflows, or just importing workflows, then the status will be the for them already.

[Deleted user]

I've the same problem.

A complete json for importing a project based on a custom workflow.

The custom workflow is inside Jira so I don't need to load it again.

the json importer is not able to resolve the statuses of the custom workflow and show an error of workflow resolution.

I need to upload tons of project with the custom workflow and this is a constraint for buying the license of Jira. Please help me.

[Nic Brough -Adaptavist-]

You need to configure the workflow correctly in the target system, so that it can cope with the incoming data.

[Ben Upham]

I also have this issue. When importing project/issue data with a JSON, the project is assigned to a "default" workflow in Jira. If any of the issues have a status that is not in that workflow, they are assigned a different status. I'd like to either specify the project workflow when importing the JSON (in the json somewhere?) or change the default workflow for JSON imports in Jira. 

[Robert Boxall]

Same issue here - seems imports only work against the default jira workflow and you can't change it. Hence imports are restricted to only allow the transitions that are part of the default. 

Best solution would be to allow the json to state the workflow to use. It probably does but the documentation is not great.

[Robert Boxall]

Well, after mining jira's own jira project I stumbled across this gem:

 "name": "Kanban Sample",
            "key": "KBS",
            "description": "Kanban Sample",
            "workflowSchemeName": "GreenHopper Workflow Scheme",
            "issues": [ 

 This solves the problem.