Hi all,
I need to update a field that is present in 2 different project through automation.
I guess I can use a multi-projects rule but I'm not sure how to define the trigger issue (to avoid that rules is triggered when doesn't require.
Here the use case:
The field "Fix version" is shared between an issue type A in Project 1 and an issue type B in Project 2. The issue B has a link "Related to" with issue B.
I want that when user update the field in the A, the value is updated also in issue B but I don't want the viceversa so the only trigger issue must be A.
Can you help me?
Thank you,
Emiliano
Resolved changing the For condition to linked issued and adding a condition that issuetype be the one I want
I tried the following automation but there a couple of issues:
1) It edited all the issues in the second project but I want to change only the issue linked with the trigger one (that is correct following the audit)
2) the Fix version field hasn't been edited in the linked issues
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, Good day. In this rule trigger will be "field value changed" and select "Fix version". Then second will be a condition, in condition either you can set "Issue type" condition (Type A) or project condition (project A). So only rule will proceed when an issue in Project A is updated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mohanraj,
thank you for your feedback.
But in this case how I know that when updating the field of issue A, only the field in the issue B (that is linked to issue A) will be updated too?
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.