Workflow Synchronization v0.8-v1.1

Video for Example configuration

Access

Workflow synchronization mapping is accessible through Administration -> Add-ons -> IssueSYNC -> Workflow Mapping

Currently there is single configuration file. It uses JSON format to save data.

Configuration format

 {
  "configuration" : [
    {
      "workflowMappingId" : 1,
	  "workflowMappingDisplayName" : "Reporting defect to support",
      "workflowId" : 10001,
      "outgoingTransitions": [
        {
          "prevStatusId" : 2,
          "currStatusId" : 5,
          "outTransitionText" : "Start progress"
        }
        ],
      "incomingTransitions": [
        {
          "inTransitionText" : "Resolved",
          "workflowTransitionId" : 41
        }
        ]
    }
  ]
}

• configuration - There is a single configuration element.
  • Next level is a mapping set. It will show up on Contract (Trigger section)
  • workflowMappingId - Enter any unique number that will identify this configuration set.
  • workflowMappingDisplayName - Provide an understandable name for your mapping.
  • workflowId - (Currently not used. For future purpose.) Enter workflowId of workflow that will be used in given configuration set.
  • outgoingTransitions - Root element for outgoing transitions configuration. It can have many children.
    
    • Next level describes single transition trigger. You issue's status change (from-status and to-status) in order to execute remote transition.
    • prevStatusId - Status that issue was before transition.
    • currStatusId - Status that issue was transitioned to.
    • outTransitionText - Control text that will be sent to remote JIRA. Based on that remote-JIRA admin can take a decision what to do (see below incomingTranistions).
  • incomingTransitions - Root element for incoming transitions configuration. It can have many children.
    
    • Next level describes single transition decision point.
    • inTransitionText - If given text will be send from remote JIRA, then execute below transition.
    • workflowTransitionId - Each workflow transition has its id. Enter the one you want to execute when given trigger text will be received from remote JIRA.
    • useRestApi - (Optional) Set this flag to true if you want to call JIRA REST API instead incode transition (that skips workflow conditions).

Exchange configuration guide

To exchange workflow configuration with remote JIRA administrator it is enough to send him:

• outTranistionText - for outgoing tranistions
• inTransitionText - for incoming transitions

Example

Below screen shows configuration for two, cooperating JIRAs.

At top, first JIRA A creates a ticket that is sent to second JIRA B. Ticket waits in OPEN status. JIRA B makes transition from OPEN to ACTION NEEDED. That triggers JIRA A to IN PROGRESS. JIRA B can BLOCK or SCHEDULED ticket without coconsequences in JIRA A but if it goes to PENDING EXTERNAL status it triggers in JIRA A RESOLVED status. From now, JIRA A can accept or reject issue sending it to REOPENED or CLOSED status accordingly. That will trigger transitions in JIRA B.

Configuration editor

Configuration editor works in two modes:

• Code (default)
• Tree

Tree mode is very handy for fast multiplying some elements. In example below new mapping is added for outgoingTransitions by selecting 'Duplicate' action from node context menu:

You can still save file on your local hard drive and use your favorite JSON editor instead. When file is ready, simply paste its content in Code mode.