You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi!
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!
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:
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.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Create rule at the Global level. This will confirm only the desired projects will trigger the rule. Works great.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Stephen Wright _Elabor8_ @Anthony Allen should these examples work on Cloud? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.