This page describes the required steps when migrating from a Jira Cloud instance to a Jira Server instance when you are using some of the default/JSU Workflow Condition/Validator/Post - Functions in your Workflow.workflows
Migration from JIRA Jira Cloud to JIRA Jira Server is directly not possible, you not directly possible. You have to be very careful as there are many validators and conditions which are built -in in JIRA cloud native into Jira Cloud, but not in JIRA Jira Server. For that, you will need JSU.
JSU Cloud's additional post - functions to JIRA makes make it more powerful with its Related Issues, Perform as a different user, and many other functionalities in the Post-functions. Using JSU's additional post-functions, you can post functions that you can use to automate your workflows without any coding.
| Info |
|---|
If you are looking Looking for documentation on a Server to Cloud migration, please follow this link? See our Migrating from Jira Server to Jira Cloud page. |
Background
Years ago, beecom donated some of JSU's modules to Jira Cloud. Atlassian integrated most of these JSU Workflow Condition/Validator/Post-Functions (based on JSU Server 1.4) into their native Jira Cloud Environment environment which were still a very very basic modules. Since then, JSU Server has added many other functionalities to make it more powerful. When JSU on Cloud was released, it also had additional advanced form of the Post-functions as of JSU Server. If you perform a migration from Jira Cloud to Jira Server, those default/JSU Workflow Condition/Validator/Post-Functions do not exist in the default Jira Server Version but can be simply replaced with the JSU Appapp.
How to fix the workflows
...
- Reconfigure the affected workflow modules with the ones from JSU. Afterwards Afterward remove the broken ones.
This is by far the safest way to do it , but can be tedious. - Export XML workflows, modify, import again.
Modify the workflows directly in the database - if you have the knowledge
It’s efficient , but very dangerous.
Workflow Condition/Post-Functions(JSU)
JSU Cloud post-functions are more powerful with its Related Issues, Perform as a different user, and many other functionalities.
...
Preconditions in JSU Cloud are built-in as a part of the post-function. You can add as many preconditions inside a post-function. But in JSU Server preconditions are implemented as a separate post-function which acts as preconditions. All the preconditions from JSU Cloud are available in JSU Server as well, but it needs they need different configurationconfigurations.
| Preconditions in JSU Server/Cloud |
| Date Compare (JSU) |
| Date Expression Compare (JSU) |
| Date Window (JSU) |
| Fields Required (JSU) |
| JQL (JSU) |
| Linked Status (JSU) |
| Regular Expression Check (JSU) |
| User Is In Any Groups (JSU) |
| User Is In Any Roles (JSU) |
| User Is In Custom Field (JSU) |
| Value Field (JSU) |
...
All other preconditions follow the a similar pattern as above. As preconditions in JSU Cloud are built-in, you have to reconfigure all the preconditions manually in JSU Server.
Workflow Condition/Validator/Post
...
Functions(Jira)
The following List list of Workflow Condition/Validator/Post - Functions which are built into the Jira Cloud Environment environment can be replaces replaced with JSU extensions. See below all attribute mappings between Jira Cloud and Jira Server.
...