Next fix version automation

[ahiggins]

Can you help me to set up an automation that automatically creates the next fix version iteration upon releasing the active one? 

I was trying to use this JQL but it doesn't seem to work: 

{{version.name.substringBeforeLast(".")}}.{{#=}}{{version.name.substringAfterLast(".")}}+2{{/}}

Thanks!

[Bill Sheboy]

Hi @ahiggins -- Welcome to the Atlassian Community!

FYI that for automation related questions, please consider posting an image of your complete rule and the audit log.  That may provide context for the community to offer ideas.  Thanks!

Two things to try:

• before you perform the math, convert the text value using asNumber() as shown here https://support.atlassian.com/jira-software-cloud/docs/smart-values-text-fields/#Smartvaluestextfields-asNumber
• If that doesn't work, split this into pieces, storing the value first in a Create Variable, and then use that variable in the math expression.

And, also the audit log can help diagnose stuff like this, so try to write your expressions to the log to see what is happening.

Best regards,

Bill

[mtaylor]

Hi Bill Aryn is my colleague this is what we have so far.

[Bill Sheboy]

Hi @mtaylor 

Please try to add the asNumber to convert the value before adding the 2 to the version.

Thanks!

[Bill Sheboy]

Hi @ahiggins  and @mtaylor 

To pause for a moment, I tried your rule as you wrote it and it worked for me as you expected.

I note you have selected a project in Create Version.  Is that the same project where this rule is stored or in a different project?

If this is for a different project, this would need to be a global-scope rule.

[ahiggins]

That's the project we want this rule to take effect. 

[Bill Sheboy]

Thanks for that information.  A couple of follow-up questions:

• Where is this rule stored: as a global rule or in the project you note?
• In the rule details, please show an image which shows the scope field

I suspect what is happing is this rule was created at the global scope, even though you just need it for one project.  The fix for that is to ask your site admin to move the rule back to Single Project scope for your target project.

[ahiggins]

Interesting! We'll have to give that a try! Thanks for your help!