Workflow conditions

Exalate provides a set of useful workflow conditions to assist you.

• 'is exalated' can be used to enable a transition once that the issue has been exalated.
• 'is not exalated' can be used to enable a transition if an issue is not linked with another issue.

See also

• Page:
  Workflow conditions
• Page:
  Unified workflow using static transitions
• Page:
  Unified workflow using global transitions
• Page:
  Configuring transition trigger to be issue type specific
• Page:
  How to unify workflows with global transitions in Jira Cloud
• Page:
  How to sync status on Jira Cloud?
• Page:
  Jira Cloud: Filtering transitions based on issue type workflow
• Page:
  Converting remote status changes to local comments in Exalate for Jira on-premise
• Page:
  Exalate for Jira on-premise: Triggering issue transition based on the value of the remote status
• Page:
  transition as proxyuser
• Page:
  How to trigger issue transition based on the value of the remote issue status
• Page:
  How to sync statuses in Jira Cloud
• Page:
  Status synchronization on Jira Server
• Page:
  How to sync statuses in Azure DevOps
• Page:
  Converting remote status changes to local comments in Exalate for Jira Cloud
• Page:
  Exalate for Jira Cloud: Triggering issue transition based on the value of the remote status
• Page:
  transition as executor
• Page:
  How to unify workflows with global transitions in Jira on-premise
• Page:
  How to convert remote status changes to local comments
• Page:
  How to sync statuses in Exalate for Salesforce
• Page:
  How to sync Date/Datetime in Exalate for Salesforce
• Page:
  How to sync statuses in Jira on-premise
• Page:
  How to sync statuses in HP ALM/QC
• Page:
  How to sync statuses in Zendesk
• Page:
  How to sync statuses in ServiceNow
• Page:
  How to sync statuses in GitHub
• Page:
  How to synchronize issue change history in Jira Cloud
• Page:
  How to synchronize statuses?