Complex conditions for Workflow Mappings

Description

Backbone is currently able to sync the workflow status only based on the workflow status. It would be great if Backbone could also consider other parameters.

Example

The same workflow exists on both sides and should be synced 1:1.
Two transitions lead from In Progress to Closed:

  • Reject: This sets the resolution to "rejected" and the status to Closed.

  • Done: This sets the resolution to "fixed" and the status to Closed.

Desired behaviour

Backbone is able to choose the same transition in the target project. The resolution (or other fields) could be used in order to define which transition should be used when.

Actual behaviour

Backbone always chooses one of the transitions.

Environment

None

Activity

Show:
Lars Lundegård
November 20, 2017, 2:47 PM

Yes I have this type of situation. Commented also BAC-753.

From Status Open - Close i have:

  1. Assign - Start working on it. Next status = Assigned

  2. Reject - Reject the issue, resolution=rejected. Next status = Closed

  3. Force Close - Close the issue, resolution=fixed. Next status = Closed

so as you describe, resolution could be used or if I could map the transition it would solve it.
The transitions exists on both sides.

Assignee

Unassigned

Reporter

Sync User [K15t]

Labels

Participants

None

QA Status

None

Deployment

None

Documentation Status

None

UI Concept

None

External Votes

None

Components

Priority

Major