According to our automation rule, when an issue is linked, the Reporter from the linked (destination) issue should be copied to the User Mailing List field in the main (source) ticket. However, we are not seeing any logs or updates for this rule.
Our goal is simple:
When an issue is linked, copy the Reporter from the linked issue and paste it into the User Mailing List field of the main ticket.
please suggest rule steps
Hello @Sachin Guttala
Please show us the rule you have built.
If you are using the Work Item Linked trigger, the rule determines which issue is the "source" and which is the "destination" based on the link used to connect the issues and how the inward and outward descriptions for that link are applied to the issues.
The rule will be triggered by the issue that is determined by Jira to be the "source" issue in the link. This is not necessarily the issue you were viewing when you created the link.
I have written up explanations on this topic in responses on two other posts:
If the rule is not triggering, then it may be that the issue that is considered the "source" in the linked pair is in a project that is not within the Project Scope of the Automation Rule. If this rule needs to operate when issues in different projects are linked, then it will need to be a Multiple Project scoped rule, and each project that might be involved will have to be specified in the rule's Project Scope.
After reviewing the explanations I added to the two posts above, let us know if you still have questions.
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.
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.
Thank you, I see the image now.
Your rule does not include a step to change the focus of the rule from the issue that triggered the rule to the linked issue(s) you want to update.
At the time your Edit action executes, the rule is still focused on the issue that triggered it, so the action is telling Jira to copy the Reporter to the User Mailing List in the same issue.
You need to add a Branch to change the focus to the linked issues.
You also need to check the Project Scope of the rule, as I mentioned previously, and ensure that it includes all the projects that contain issues that might be used in the links you create.
And, as I also mentioned, you need to consider how you are linking the issue together; which would be considered the source and which the destination. Otherwise the data may not copy in the direction you expect.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill @Trudy Claspill i have tried altering automation but i am not seeing success please help , i have attached rule details
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Sachin Guttala
We will need more details to debug this.
What issue were you in when you created the link?
What issue did you link it to?
What link type did you use? Can you provide a screen image from the issue showing the Linked Issues section?
From which of that pair of issues did you expect the Reporter to be copied?
What were the actual results you observed?
Can you provide screen images showing the details of the rule Audit Log, expanding all the details of the entry for execution of the rule? That entry will show you the issue key of the issue that triggered the rule, and the issues that it found through the Linked Issues branch, and the outcome of the Edit action.
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.