Assume you want to setup a connection between a software vendor and one of their customers. The challenge is to create a unified workflow so that each party can work on their own tracker, but that the issue is handled by both.
This example shows how you can construct your relations so that the right transition is selected. Also check 'Unified workflow using global transitions' for another approach where the transitions in both workflows are global.
The scenario is as follows. Two issue trackers - 'blue' and 'red' - blue is being used by the customer, red by the software vendor. The blue workflow has been setup to reflect the remote issue status, while the red workflow is a simple three stage issue workflow.
The unified workflow main path is depicted below:
- Customer raises an issue and exalates it to the software vendor.
- A new issue is created automatically.
- The software vendor starts working on the issue.
- The customer issue is automatically progressed to status 'Remote progress'.
- The software vendor completes the implementation, and progresses the issue to 'Resolved'.
- The customer issue changes status automatically to 'Remote resolved'.
- The customer reviews the implementation and confirms by closing the issue.
- The software vendor issue is automatically closed.
Blue issue tracker
Red issue tracker