Expand all   Collapse all

Platforms



Skip to end of metadata
Go to start of metadata

Problem

Known issue for Exalate 0.13.8 and lower.

 

On a unidirectional relation, if you try to exalate an issue towards an empty Create processor, you expect no changes on the issue after running the processor.

Scenario

  • Uni-directional relation
  • Sync from JIRA A to JIRA B
  • Create processor is empty on JIRA A
  •  Exalate an issue FROM Jira B TO Jira by accident

Actual error

  • An issue create attempt is made
  • This attempt fails

Expected behavior

  • The request is canceled (because the JIRA A Create processor keeps the issue unmodified)

Resolution

Upgrade Exalate add-on (bug was fixed in 0.13.9).