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:
import procedure on another Jira instance:
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?
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- 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.
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.
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".
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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!
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