Status Synchronization
Your JIRA workflow can be synchronized:
- one-to-one (assuming remote workflow is same as local)
- partially at some defined status transitions
Here is an example of two different workflows synchronization. You may notice that:
- Open → In Progress is mirrored
If someone will click in progress, it will be reflected in second JIRA. - Closed → Open is one way
Only if left side will reopen issue, the transition will be executed on remote JIRA.
| Info |
|---|
Workflow transitions are made on behalf of Technical User. |
| Info |
|---|
Workflow Synchronization is setup by Administrator. It may be not clean on issue what are synchronization points. You will need to ask your Administrator for details. |
Workflow as Trigger
Workflow transition can be also used as a trigger to:
- Create remote issue
When issue reach given stage it can be replicated (for example in Service Desk: forward to 3rd line support).
- Update remote issue
You don't need to synchronize all field changes over and over but maybe at some point in workflow you may want to push that changes to remote JIRA.
Transition with required fields
When you want to synchronize workflow and you have some fields, which are required to fill before transition will take place, then you have to alter your workflow.
IssueSYNC sends information containing only transition and resolution during workflow synchronization process, fields are synchronized by different process.
Below you can find example, which shows what you have to modify to obtain fully synchronized transitions.
- Let's assume your workflow looks like this:
- On "Close" transition you require from user to fill Component/s field:
- Probably you would have mapped workflow just like:
- Close transition won't take place, so you need to adjust your workflow. Below you you can find required steps:
- add new transition from status "IN PROGRESS" to status "CLOSED", e.g. IssueSYNC_close, without attaching Screen to it
- add condition to this new transition (IssueSYNC_close), restrict it to technical user only (because there is no condition for single user, you need to create new group and assign technical_user only to this group, you will ensure no one will have access to this transition excluding technical_user, which will allow IssueSYNC plugin to make transition)
- Alter your IssueSYNC's workflow mapping scheme (map only transition without required fields as below):
- add new transition from status "IN PROGRESS" to status "CLOSED", e.g. IssueSYNC_close, without attaching Screen to it
- You are all set.