nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues setting a custom field from linked issue

unknown

Hello, I have the below requirement.

Project A has a custom field named CausedByIssueKey. I want to populate this using an automation rule with the value of key from Project B. An issue from Project B is linked to an issue in Project A using the "caused by" relationship.

I tried following multiple pre-existing articles on this topic but am not able to make it to work.

Please help with specific steps to take to make this automation rule work.

Thanks in advance.

Accepted answers

Trudy Claspill

Hello @[deleted]

What event should cause the rule to execute?

Is this going to be a scheduled rule?
Do you want the rule triggered when the value of in an issue in Project B changes?
Do you want the rule to run when an issue from Project B is linked to an issue in Project A?

Can the issue in Project A be linked to more than one issue in Project B with the same link relationship?

unknown

Hello @Trudy P Claspill

1. It will be an automation rule.

2. It will be triggered when an issue in Project A is associated with an issue in Project B with the "caused by" relationship.

3. Correct, when an issue from Project B is linked to an issue in Project A. This is because issue in Project A will be created only if the issue in Project B pre-exists.

4. It is possible that issue in Project A can be linked to more than one issue in Project B but for simplicity we can assume there is only one such link.

5. If it simplifies things then both the issues in Project A and Project B will be epics in my use case.

Thanks.

All comments

Trudy Claspill

Hello @[deleted]

What event should cause the rule to execute?

Is this going to be a scheduled rule?
Do you want the rule triggered when the value of in an issue in Project B changes?
Do you want the rule to run when an issue from Project B is linked to an issue in Project A?

Can the issue in Project A be linked to more than one issue in Project B with the same link relationship?

unknown

Hello @Trudy P Claspill

1. It will be an automation rule.

2. It will be triggered when an issue in Project A is associated with an issue in Project B with the "caused by" relationship.

3. Correct, when an issue from Project B is linked to an issue in Project A. This is because issue in Project A will be created only if the issue in Project B pre-exists.

4. It is possible that issue in Project A can be linked to more than one issue in Project B but for simplicity we can assume there is only one such link.

5. If it simplifies things then both the issues in Project A and Project B will be epics in my use case.

Thanks.

Trudy Claspill

Do you have any administrative access in Jira? Are you a Project Administrator for either or both Project A and Project B? Are you a full Jira Administrator?

Because this rule involves multiple projects it will need to have a scope that includes both projects. Only a Jira Administrator can create a rule that has multiple projects in its scope. If you are not a Jira Administrator you will have to get a Jira Administrator to create the rule for you.

Making sure that I understand the relationship you are creating, which of these is correct?

B-111 is caused by A-222
A-222 is caused by B-111

unknown

1) I am an administrator just for my project which is Project A.
2) Not an administrator for Project B.

3) Not a full Jira Administrator.

Relationships would be as below.

B-11 exists first and then A-222 is created.

A-222 is caused by B-111.

B-111 causes A-222.

Thanks.

Trudy Claspill

I can share the automation rule here, but if you are not a full Jira Administrator you will not be able to implement it in your instance. You will have to work with a Jira Administrator to get that done.

Here is the rule:

Screenshot 2024-03-12 at 9.52.29 AM.png

In my instance "Problem/Incident" is the name of the link type that provides the "causes"/"is caused by" relationship.

When you use the Link Issues trigger, that is a special case where the rule is actually triggered by the issue that shows the Outward Description part of the link relationship. So, regardless of whether you create the link from the Project A issue or the Project B issue, the rule is triggered by the issue that shows it "causes" the other issue. In the below screen image issue CS-85 displays that it "causes" CMSB-11, so it is CS-85 that is the issue triggering this rule.

Screenshot 2024-03-12 at 10.00.26 AM.png

With the Link Issue trigger the rule has a special option to recognize one of the issues as the "source" issue, and one as the "destination" issue. The one that is the "source" is the one that triggered the rule. The issue to which it has been linked is the "destination" and can be referenced with the special smart value {{destinationIssue}}

The conditions after the trigger ensure that the rule will continue to process only when it is triggered by a link being created from an issue in Project B to an issue in Project A. This is necessary because the Rule Scope must name both projects. Without these conditions the rule could execute when an issue in Project A was linked as "causes" an issue in Project B.

You want to update the issue in Project A, but with this rule it is the issue that is in Project B that triggered the rule. So you need to use a For Branch component to change the focus to the issue in Project A. Because the Link Issue trigger is used, we can use a special option in the For Branch to specify changing the focus to the "destination" issue in the linked pair.

And then, lastly, you use an Edit action to edit your custom field in Project A to add the value from the source issue (Project . Because the source issue is the one that triggered the rule you can use the smart value {{triggerIssue}} to reference that issue. I used the Summary field in my example.

Screenshot 2024-03-12 at 10.09.54 AM.png

unknown

Hello @Trudy P Claspill - these are the steps I followed. I did not get the expected result.

Rule layout (project names erased - first Project-B and second Project-A)
Step 1.png

When block

Project Equals (1st - Project-B)
Step 3.png

Project Equals (2nd - Project-A)

For block

Then block (field is Dependency and is chosen)

Tests :

1) While in Issue-1 of Project-B, create a causes link to Issue-2 in Project-A

Expectation : Dependency Field in Issue-2 of Project-A is set to Issue-1

Result : Dependency Field in Issue-2 of Project-A is blank

2) While in Issue-2 of Project A, create a caused by link to Issue-1 in Project-B

Expectation : Dependency Field in Issue-2 of Project-A is set to Issue-1

Result : Dependency Field in Issue-2 of Project-A is blank

unknown

@Trudy P Claspill - You might ask for the audit log. So, here is the image. Rule did not trigger.

Step 7.png

Trudy Claspill

Sometimes there is a delay in the updating of the Audit Log screen. Please check it again to see if logs have shown up.

Please show us the information from the Issue Linking configuration screen that shows the Inward and Outward Descriptions for the "Cause" link type.

https://yourBaseURL/secure/admin/ViewLinkTypes!default.jspa

Additionally the two conditions that you have immediately after the trigger are going to block the rule from executing. In this scenario you can't use the Issue Fields Condition. You need to use the {{smart value}} Condition

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud