Automation rule for creation of Fix Versions across multiple projects

[Miles Tillinger]

As per the questions, I'm seeking an exemplary pattern for automating creation and maintenance of Fix Versions across multiple projects.

Some of the scenarios I need the rule to cover:

• Bulk project creation: Create the same Fix Version across multiple specified projects simultaneously
• Template-based creation: Apply standardised version naming conventions (Eg. v2.33 (d/M/Y))
• Conditional project inclusion: Only create versions in projects that meet certain criteria (perhaps project category, or a list in a custom variable)
• Automatically create corresponding Cross-Project releases in Jira Plans when Fix Versions are created
  
• Status propagation: Automatically update version status (unreleased → released → archived) across all linked projects

I'm sure I'd discover more requirements as I go!

Thanks in advance for any suggestions.

[Valerie Knapp]

Hi @Miles Tillinger , welcome to the Atlassian Community and thanks for your post.

It should be possible to create multiple Fix Version / Releases in a single automation like this -

You could just copy the 'create version' action and then indicate the different projects in each action. In this way, you also have control over the naming. You could use, as the description under the Version name suggests, smart values to enforce a naming convention.

Please test something like this and let us know how you get on, if you get stuck or need more help.

Best wishes