I have 2 project A and B.
All B's issue is cloned from A based on certain trigger.
To reduce the duplicated work, I want to set a rule to: when issue in B is updated, its linked issue in A will also update the status. This should only apply to these same issue, not any other issues within A or within B with a relationship of linked.
How should I set that automation rule?
Hello @Weiwei Zheng ,
You can create an Automation rule,
Trigger: When Field Value changes (select all the field, you want to sync between A and B)
Branch: Under Branch rule / related issues; from Type of related issues, select Linked Issues and then under Link Types (select the link you have between A and B)
Action: Edit issue, (Select all the fields to be synced and copy it from Trigger issue)
NOTE: Please create a special Link Type for this, so that no other tickets linked are considered
This is the rule I currently set, can you take a look and let me know where it went wrong?
The field I am planning to sync is "status" only. However, based on this rule, the tickets within project A are also update status whenever they have linked issue as cloned which is not planned.
FYI: As the ticket in project B is cloned from project A, I set the rule for linked issue as "cloned", and we have several tickets with the same link type as cloned.
can we set the rule as only sync between Project A and B?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Weiwei Zheng
You will have to do couple of changes
1. You will have to create unique link, cloned link type is common and can be used by many issues. Suggestion is to create a unique link; you can do that by modify your automation Rule where this cloning is happening.
2. Once you have created that unique link type you can update your existing automation Rule where you have selected Type as all linked types to that specific link type.
If you don't want to add the new link type and want to continue with clone, you use any field as a condition to separate it form other cloned tickets
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.