Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Getting error when trying to match a multiselect dropdown to Fix Versions

When trying to connect a custom multiselect dropdown field to the Fix version field via automation, I receive an error: Screen Shot 2021-02-02 at 5.46.34 PM.png

The Fix versions and the multiselect dropdown fields have the same values and are apart of the same project which is odd. I was able to automate these fields together when using a single field but needed to change the automation code to account for multi selections. 

Here is a screenshot of my automation set up: 

Screen Shot 2021-02-02 at 5.49.16 PM.png Screen Shot 2021-02-02 at 5.50.04 PM.png

Any idea what the issue might be here? Thanks for any help in advance! 🙏🏼

1 answer

1 accepted

0 votes
Answer accepted

Hi @Alex Degregori 

Looking at your rule, when the Custom Sprint field changes, you are trying to set the Fix Version to the previous values of the Custom Sprint field.  Is that correct?

First thing, I suggest putting in an audit log action for the value you are trying to set to the Fix Version.  That will confirm if the value is indeed a value version.

Next, you note the Custom Sprint field is multiple selection and you are using the changelog syntax.  Are you expecting multiple values in the Custom Sprint field to be set to Fix Version?  If so...

  • I have not nested list functions before (changelog and custom field).  Writing to the audit log, as I noted earlier, should help see if that works.
  • If it does, you will need to make the list of values comma-separated in order to set the Fix Version, but you have a single set of quotation marks around the listed values.  With nested lists you may need to experiment with that, perhaps using split and join to wrap the items properly.

Best regards,


Hey Bill! Thanks for the extra context. I actually posted this in the generic Community question pool and got an answer there. So I'll close this out as answered as well. 

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,757 views 2 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you