Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

1 vote
Answer accepted

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?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

222 views 2 1
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