I have created a custom workflow + new screen + few custom fields on my test Jira environment. Exported this workflow, and tried to import in production Jira instance, but I see that only workflow is imported, not the related screens and custom fields in theat screen Following are the details about my workflow: * First created new custom fields * created new screen using these custom fields * created new workflow and assigned above screen to a transition. Export procedure: * opened workflow in view mode * exported as workflow (not xml) import procedure on another Jira instance: * imported the .jwb file * On final import confirmation page, I saw that Jira detected only workflow stated, and not screens and custom fields. * After import, cannot see screen and custom fields in system. I was under impression that if custom fields are included in screen which is attached to workflow transition, then it should be automatically included in workflow .jwb export. But it's not working, can anyone point me to solution?

I've tried to export my workflow with custom fields and screens from our DEV environment and import into PROD and none of my custom fields or screens are coming over. I'm doing a workflow export (jwb) not xml. During the export process, it is clear that it isn't picking up the screens and fields. This documentation implies that custom fields are brought over in the jwb import:https://confluence.atlassian.com/adminjiraserver075/sharing-your-workflow-935391429.html#Sharingyourworkflow-Customfieldsinworkflowimports My custom fields haven't been disabled. Am I missing something? Thanks!

Thanks Nic, while testing i found the same, new statuses were created for those which was not part of the Jira earlier. Thanks Philip.

To save your testing - you're right, the IDs of things not in the workflow (i.e. transitions) will change. They have to, as the target Jira will not be in the same place as the source and could easily have the incoming ids. It treats all the incoming config as "new".

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira workflow export not including screens and custom fields

unknown

I have created a custom workflow + new screen + few custom fields on my test Jira environment. Exported this workflow, and tried to import in production Jira instance, but I see that only workflow is imported, not the related screens and custom fields in theat screen

Following are the details about my workflow:

First created new custom fields
created new screen using these custom fields
created new workflow and assigned above screen to a transition.

Export procedure:

opened workflow in view mode
exported as workflow (not xml)

import procedure on another Jira instance:

imported the .jwb file
On final import confirmation page, I saw that Jira detected only workflow stated, and not screens and custom fields.
After import, cannot see screen and custom fields in system.

I was under impression that if custom fields are included in screen which is attached to workflow transition, then it should be automatically included in workflow .jwb export. But it's not working, can anyone point me to solution?

Accepted answers

All comments

Nic Brough -Adaptavist-

Fields and screens are NOT part of the workflow. They are configured in Jira and then referred to (if needed) by the workflow.

I'm not sure where you got the impression that they are in the workflow from. You will need to create supporting screens and fields in the target Jira if you want to move a workflow from one system to another (without using a workflow bundle)

unknown

@Nic: take example of following workflow from marketplace- https://marketplace.atlassian.com/plugins/com.atlassian.workflow.bundles.recruitmentworkflow

when I import this workflow, along with states, it does import screens and custom fields. please find attached import screenshot as proof of this.

Nic Brough -Adaptavist-

Sounds like you have used the standard export and not a Jira workflow bundle - that's what my answer was about.

unknown

I did use Jira workflow export, and not simple XML export. Exported file was with JWB extension.