Skip to main content
Version: 2.0.0

Escalation from a workflow

To create a remote work item during a transition, configure the Cross-Site Sync validator and post function on the same local workflow transition.

Configure the transition​

  1. Open the local project's workflow configuration and edit the workflow.
  2. On the transition that should escalate the work item, add the Cross-Site Sync – Validate destination requirements validator.
  3. On the same transition, add the Cross-Site Sync – Escalate to destination post function.
  4. In the post function configuration, select an active rule with the Transition trigger for that project and work item type.
  5. Check that the transition screen lets users complete any required fields sent to the remote site.
  6. Save and publish the workflow. Test the transition with a representative work item.

The validator checks the destination's required fields before allowing the transition. If a value is missing, the transition is blocked and Jira indicates which field to complete. Add the necessary fields to the transition screen so the user can correct them.

The post function creates the remote work item using the rule's mappings. When it finishes, the app adds a comment with the remote key to the local work item. If creation fails, check the work item notice and the latest error in the panel.

Prevent duplicates and resolve errors​

Escalation is idempotent: running the transition twice, retrying it, or receiving a delayed response does not create a second remote work item for the same rule and local work item.

If a rule uses a field value trigger, Jira does not block the transition when a required remote field is missing; the app reports the problem on the local work item. Fix the mapping or value, then retry from the panel when the connection is available.

For Manual only triggers, you do not need a post function. A user with edit permission can select Escalate in the panel. See the panel guide.