Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Automation: Create a version in another project


Is it possible that a version is created in Project B, when a new version is created in Project A. The version should have the same name, etc in both projects. I'm using two classic projects and have not found the appropriate actions in the Automator.

Thank you!

2 answers

1 accepted

2 votes
Answer accepted
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 08, 2020 • edited

Hi @Bodavo 

You can sort of do this.

The issue is automation rules mainly run based on issue triggers - or, against issue actions. Rules which are project release-based aren't the norm.

So I created this rule:

  1. Trigger: Version Created - In "More Options", I entered a unique identifier into the "Version name filter"
  2. Action: Create Version - in "Version name" I put "{{}}". Then via "More Options", for "Version Release Date" I put "{{version.releaseDate}}", and I chose a target Project

I could not locate a way to base the Trigger on a specific project - so the unique identifier lets the rule know which versions trigger the rule, and which do not.

There also doesn't appear to be an option to set Version Start Date on the action - just name and release date.

Furthermore, I found this only worked as a global rule. I assume this is because if you place it in the trigger project's rules, it can't create in the target project - likewise if it's in the target project, the rule is only checking it for version creation, not all others.

It's a workaround but it is an option - if you can ensure these versions have a unique identifier not used elsewhere on your instance.


Thanks for your detailed explanation!

Create rule at the Global level. This will confirm only the desired projects will trigger the rule. Works great.


Hi Anthony, i can't make it. You can helpme?

Kelly Arrey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 27, 2022

@Stephen Wright _Elabor8_ @Anthony Allen should these examples work on Cloud? Thanks!

@Kelly Arrey I would think so but cannot say for sure, as we are on Server.

Like Kelly Arrey likes this

@Surizaday Morones Apologies just seeing this. If you can tell me what you're experience and/or what your audit log says, I might be able to.

Thanks for this. Is there a way to sync the versions as well.. let's say I released the version in Project A, the same version on Project B should be changed to released as well?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events