Affected Version won't sync from project A to project B

General Questions
, , ,
1

Originally asked by Destri Weir on 28 January 2022 (original question)

I’m using Jira Cloud with a Visual Sync and some scripting. Right now my sync is working perfectly for everything except for Affects version. We have automation that creates the versions in all projects when it’s created in one, so it’s not an issue of the version not existing.

Also, prior to deciding to move to a visual sync plus script when I was just using script, the version sync was working just using the replica.version = issue.version code, but that also doesn’t work in this case.

I am using a direct cut and paste of the script suggested here: https://docs.idalko.com/exalate/display/ED/Script+rules+examples

Here is my script:

// assign fix versions from JIRA A to JIRA B
ServiceDesk.fixVersions = Main
.fixVersions
// ensure that all the fixVersions are available on B
.collect { v -> nodeHelper.createVersion(issue, v.name, v.description) }
// assign affected versions from JIRA A to JIRA B
ServiceDesk.issue.affectedVersions = Main
.affectedVersions
.collect { v -> nodeHelper.createVersion(issue, v.name, v.description) }

2

Answer by Francis Martens (Exalate) on 29 January 2022

Did you check the content of the Main.affectedVersions?

Incoming | Untested

debug.error("Main.affectedVersions = ${Main.affectedVersions.properties}")

Comments:

Destri Weir commented on 31 January 2022

Can I do this sort of debugging with Jira Cloud?

Francis Martens (Exalate) commented on 31 January 2022

Yes. the debug.error results in an error containing the provided message

Give it a try.

Destri Weir commented on 31 January 2022

Thank you! Using that info and the info here: https://docs.idalko.com/exalate/display/ED/How+to+use+scripts+in+Visual+connections, I was able to get the version sync to work.