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.
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.
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...
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