Initial status is not considered for workflow mappings

Description

Backbone does not consider the inital status of a workflow mapping - and therefore an issue may be in the wrong status.

Steps to reproduce

  1. Create a synchronization with a workflow mapping which maps the initial status of project B, e.g. Open, to some status of project A, e.g. "in progress" (it's important that it's not mapped to the initial one)

  2. Create an issue in project B

  3. Check the status of the issue

Expected result
The status of the issue in project A should be the mapped one, e.g. "in Progress".

Actual result
The status of the issue remains in the initial state, e.g. "Open"

Workaround
If you perform a resync from B to A for this issue and check the "current status" checkbox, the status is properly propagated.

Environment

None

Assignee

Unassigned

Reporter

Sync User [K15t]

Labels

None

Participants

None

QA Status

None

Deployment

Cloud
Server

Documentation Status

None

UI Concept

None

External Votes

None

Priority

Major