It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira workflow export not including screens and custom fields

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?

1 answer

0 votes

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)

@Nic: take example of following workflow from marketplace-

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

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

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

Ummm. Is there an answer for this? I'm about to attempt the same scenario...export to JWB file and import to a separate JIRA instance. This will save me a LOT of time if it works. I'm using JIRA 6.3.10 The discussion seems to have ended on an inconclusive note.

I have tried this out myself and it is true that screens and custom fields are imported when you import a workflow into JIRA Server from a .jwb file. I exported a workflow with 1 screen and 3 custom fields associated ('As Workflow' to .jwb file) from a JIRA 7.3 instance. I then imported it into a JIRA 6.3 instance. The screen and custom fields were created when the workflow was imported.

Hi Philip, just a questions,

Let's say you imported from JiraA to JiraB(using jwb not xml).

& now JiraB has whole new set of Screen & custom fields.

Question 1: Is the custom fields in JIRAB has same ID as JiraB?

Question 2: were status also created? if yes does they have same transtionID as earlier.

Hi Mahesh,

it is a while since I played around with this. The JWB export-import method is designed to assist you create the dependencies you need when moving a workflow, such as statuses, screens and custom fields. I believe there is no guarantee that IDs will remain the same, although I have not tested this.

In your example, JIRA B may already have a different custom field or status with the IDs used in JIRA A - so there may be a conflict.

Why not try this yourself and post the result here?

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".

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

Thanks Philip.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Apr 09, 2019 in Portfolio for Jira

Portfolio for Jira 3.0 is here!

The wait is over... Portfolio for Jira Server and Data Center 3.0 is now officially here! Platform releases offer Atlassian an opportunity to shift our strategy, make bold predictions about t...

1,383 views 14 26
Read article

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