Automate population of Affects Version field

Nicole Baratta

I'm setting up an automation that is creating a new issue in a different Jira project and I can't seem to get the Affects Version field to carry over. I tried doing it with the 'Choose fields to set from' pull down, but the ID for the version is different in both projects even though the name is the same.  So I tried to do it in the 'More options' with :

{
"fields": {
"versions" : { "name": "{{versions.name}}"}
}
}

But it's not working either.  If I put 

Affects Version: {{versions.name}}

In the Description field, the right thing does show.  Am I doing something wrong in the 'More Options' section? 

Bill Sheboy

Hi @Nicole Baratta 

Without seeing your rule details...It seems you are trying to copy that field from one project to another, and the number of values to use in the JSON is unknown.  Correct?

If so, you would need to build the expression using list functions and then place that in the JSON.

You have already identified the correct smart values and syntax for Affects Version.  Let's assume your source is the {{triggerIssue}} for the rule.  The JSON would be something like this:

{
    "fields": {
        "versions" : [
            {{#triggerIssue.versions}} { "name" : "{{name}}" } {{^last}}, {{/}} {{/}} 
        ]
    }
}

If that doesn't work because of the nested brackets, consider building the expression from the list as a created variable, writing it to the audit log to confirm it, and then inserting that variable into the JSON.

Kind regards,
Bill