Remove issue from future sprint with automation

[Dmytro Mykytenko]

Hello,

I'm trying to put together an automation rule that would remove issue from any future sprint while keeping it in any other - active or closed - sprints (if there are any - could be anything from 0 to N). I know that I can completely clear sprint field but that is not what I'd like to achieve. 
I can extract details of a sprint(s) to be removed in smart variable and I can get names of past (closed) sprints, but how can I update sprint field to set multiple values at once?

[Christopher Maxwell]

Hi Dmytro,

Welcome to the Atlassian Community!

Are you wanting to prevent an issue from having any new sprint added to it?

[Dmytro Mykytenko]

Hi Christopher,
I want to remove any sprint(s) which match futureSprints() from an issue and keep other sprints (if any) intact. An issue may be added to several sprints having variable states  when the rule is fired.
Prevention is nice to have too, but it's not so important.

[Christopher Maxwell]

Hi Dmytro,

When creating the automation, have you tried utilizing the "More options" with your smart variables? While I do not have experience with the field, it may provide what you need. 

Some support information:

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Jiraautomationactions-Editissue:~:text=Log%20in-,Atlassian%20Support,Edit%20issue,-Use%20smart%20values

As well as:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-json-functions/

[Dmytro Mykytenko]

Hi Christopher!

Thank you for this suggestion. I need to investigate if it is possible to use JSON functions and chaining together with regexp to achieve required result.

[Christopher Maxwell]

Hi @Dmytro Mykytenko I'm circling back through some of my posts and wanted to check and see if you've made any progress here? If so, would love to know what you found out - and, at the same time, would be great then to mark the ticket as "answered" so it's not still showing as pending/open.

Have a great week!
Christopher

[Dmytro Mykytenko]

Hi @Christopher Maxwell 
I decided to take different approach in the end, and just added another check so these issues can be identified and displayed easily - as these cases are quite rare for us it is OK to handle them manually. I realize that I have drifted quite far from my original question, but I have nothing to add as for today. 

Best regards,
Dmytro