Issue Summary

When updating a fix version into project A, if you need to build an automation to update the same changes into project B, it's not possible so far. There's no way to store the last values from the fix version into project B so that when it changes in project A, there's no way to compare and find which is the same fix version into project B to update it.

Steps to Reproduce

• Create a fix version
• Create an automation to POST the same fix version into another project (web request)
• Then try to create an automation with the "fix version updates" trigger to execute each time the fix version A have fields changed and to send this changes to project B.

Expected Results

• The automation should find the fix version into project B and update it with the new values set in project A.

Actual Results

• As we've already changed the values in project A, the automation can't match the fix versions between those projects. Cause into the project B, the fix version has the old values (and another ID as it's another project also).

Workaround

• There's no workaround so far.