Hi all, When I update a ticket, I want it to look at the first inward ticket and update the current issue field value to the same value to the inward value. Apologies if I'm using the word "inward" the wrong way around. I wrote it maybe better here: * I have 3 issues linked in a chain, A >B > C * A has value x, B and C have no value. * On B update I need it to copy the value from A. * On C update I need it to copy value from B. Is this possible and how? In our email we use {{issue.issuelinks.first.inwardIssue.issuetype.cf0000}} which works great and I think will work here. But I cannot get this to work for edit issue nodes. Thanks

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; } } }

Jira Automation - Field update to edit current field value based on an inward linked field value

Hunter1428

Hi all,

When I update a ticket, I want it to look at the first inward ticket and update the current issue field value to the same value to the inward value.

Apologies if I'm using the word "inward" the wrong way around.

I wrote it maybe better here:

I have 3 issues linked in a chain, A >B > C
A has value x, B and C have no value.
On B update I need it to copy the value from A.
On C update I need it to copy value from B.

Is this possible and how?

In our email we use {{issue.issuelinks.first.inwardIssue.issuetype.cf0000}} which works great and I think will work here. But I cannot get this to work for edit issue nodes.

Thanks

Accepted answers

Bill Sheboy

Hi @Hunter1428

If I understand your question correctly, I believe you can do that with a branch using JQL, matching the key on the link from the triggering issue.

Perhaps try that and if there are problems, post an image of your rule and audit log to see how the community can help. Thanks!

Best regards,

Bill

All comments

Bill Sheboy

Hi @Hunter1428

If I understand your question correctly, I believe you can do that with a branch using JQL, matching the key on the link from the triggering issue.

Perhaps try that and if there are problems, post an image of your rule and audit log to see how the community can help. Thanks!

Best regards,

Bill

Hunter1428

Hi @Bill Sheboy

Thanks for the quick reply!

I understand what you mean but I'm still struggling to get this to work.

Also here is some more detail to hopefully clarify on what I need

What I don't want to happen is when A is updated to send the value to B. I need it the other way around.

When B is updated, I want it to take the value from A.
Same for C, I want it to take the value from B and not when B updates to send the value to C

So if C is added to the end of the chain and B has not yet updated to take the value from A, then C also will also not get the value as it's not present in B.

I can easily get A to send the value to B when A is updated. But I don't want to update A to pass the value to B, because this would be sending the value down the chain. I need the lower items to take the value from above if possible.

Thanks!

Bill Sheboy

Hi @Hunter1428

Sorry, I just noted you are on server and not cloud. There are some cloud features that would have helped, but I believe you can still do this... For your version I suspect you may need to turn this problem inside out and use two rules:

First rule:

Trigger: issue updated (with whatever conditions you need) e.g. ISSUE-B
Condition: has a linked issue per your conditions e.g. ISSUE-A
Action: do what you need to do for the updated issue e.g. ISSUE-B
Branch: on the linked issue e.g. ISSUE-A
- Action: update the linked issue (e.g. comment) to indicate it needs to pass on the value e.g. ISSUE-A

Second rule (with Allow rule trigger enabled):

Trigger: detect the comment added from the first rule e.g. ISSUE-A
Branch: on the linked issue from the first rule e.g. ISSUE-B
- Action: edit the linked issue with the value from the trigger issue e.g. value from ISSUE-A goes to ISSUE-B

Hunter1428

Hi @Bill Sheboy

This is great, it worked perfectly. Thank you very much for you help with this!

I'm going to try and see if I can get this working on 1 automation and without the need to affect multiple tickets. But it works, so it's a starting point!

Thanks again!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

addon-com.codebarrel.addons.automation

jira-server

automation