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

Getting the parent issue key in automation

Jamshaid

I have two projects TM and CO. When in TM, an issue is created, same issue is cloned to CO and a Cloners link is created between both issues.

What I want to do is that when the issue in CO is transitioned to Done, it should send a web request having the key of parent issue in TM project in its parameters or body. I am unable to get the link between both issues. Here is what I have tried

But, this condition never triggered. It always ends up with this response

I am unable to get what I should do regarding this as I am totally new to automation in Jira.

Thanks

Accepted answers

Jamshaid

I had to transition the linked issue to Done state and send a web request containing the parent issue key. Here is how I did it. I created a shared rule between both projects and then used the following automation flow to close the issue and send web request.

Screenshot from 2024-02-26 21-34-45.png

All comments

Rudy Holtkamp

Hi @Jamshaid ,

Maybe you should use 'cloned by' instead of 'clones' in the branch.

It depends how the two issues are linked.

Jamshaid

@Rudy Holtkamp Even if i use is cloned by, it throws the same message in logs

Rudy Holtkamp

The log says that it can't find a linked issue of the link type 'clones'.

So you might want to take a closer look to the issue by using:

https://yoursite.atlassian.net/rest/api/latest/issue/CO-17?expand=names

Then search for 'issuelinks', you should see something like this:

"issuelinks": [
  {
    "id": "10762",
    "self": "https://rudy.atlassian.net/rest/api/2/issueLink/10762",
    "type": {
      "id": "10001",
      "name": "Cloners",
      "inward": "is cloned by",
      "outward": "clones",
      "self": "https://rudy.atlassian.net/rest/api/2/issueLinkType/10001"
    },
    "outwardIssue": {
      "id": "11999",
      "key": "RUDY-15",
      "self": "https://rudy.atlassian.net/rest/api/2/issue/11999",
      "fields": {}
    }
  }
]

Note: I use Chrome with an extension called JSON formatter.

Jamshaid

@Rudy Holtkamp this is the relevant output

 "issuelinks": [
{
"id": "10656",
"self": "https://mysite.atlassian.net/rest/api/2/issueLink/10656",
"type": {
"id": "10001",
"name": "Cloners",
"inward": "is cloned by",
"outward": "clones",
"self": "https://mysite.atlassian.net/rest/api/2/issueLinkType/10001"
},
"inwardIssue": {
"id": "11214",
"key": "TM-63",
"self": "https://mysite.atlassian.net/rest/api/2/issue/11214",
"fields": {
"summary": "test211",
"status": {
"self": "https://mysite.atlassian.net/rest/api/2/status/10001",
"description": "",
"iconUrl": "https://mysite.atlassian.net/images/icons/status_generic.gif",
"name": "Done",
"id": "10001",
"statusCategory": {
"self": "https://mysite.atlassian.net/rest/api/2/statuscategory/3",
"id": 3,
"key": "done",
"colorName": "green",
"name": "Done"
}
},
"priority": {
"self": "https://mysite.atlassian.net/rest/api/2/priority/3",
"iconUrl": "https://luminsec.atlassian.net/images/icons/priorities/medium.svg",
"name": "Medium",
"id": "3"
},
"issuetype": {
"self": "https://mysite.atlassian.net/rest/api/2/issuetype/10101",
"id": "10101",
"description": "A problem which impairs or prevents the functions of the product.",
"iconUrl": "https://mysite.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium",
"name": "Bug",
"subtask": false,
"avatarId": 10303,
"hierarchyLevel": 0
}
}
}
}
],

Kalyan Sattaluri_iinm1n

@Jamshaid Is your TM project available in scope from the rule of CO project?

I just tested a similar set up and if the cloned issue is within the same project, branch logic like you have picks it up as expected but if you dont have "scope" then you wont get the key from TM project.

So if thats the case with you and that is why you are not able to get the key, I was thinking of below approach which is without the branch logic.

But please confirm above step as thats the easiest route or work with your admin if you can be granted that scope.

My proposal was, Before your branch, first please try to log below smart value, should pull the list of keys.. modify the if condition accordingly.

{{#issue.issuelinks}}{{#if(equals(type.name,"Cloners"))}}{{inwardIssue.key}}{{^last}}, {{/}}{{/}}{{/}}

You then convert this into a list by first storing above smart value into a variable (myvar) and doing a split. {{myvar.split(", ")}}, now you have a list of keys.

If you want to loop through and make a web request call for each of "parent" /original cloned link, I believe you can do an "advanced branch" afterwards on {{myvar.split(", ")}} and make your web request calls for each "key" that way. Something along the lines of below thread or similar posts which loop over a list.

https://community.atlassian.com/t5/Jira-Service-Management/Automation-loop-through-WebResponse-results/qaq-p/2140920

hope it helps. If this is not what you are thinking of, please help explain what do you want to do.

Jamshaid

@Kalyan Sattaluri Thanks. I am not really concerned about using branch logic. I just want to get the key of the parent issue. It is supposed to be only one having the current logic.
I will try your solution.

Kalyan Sattaluri_iinm1n

@Jamshaid Sure, Just edited my post with screenshot, please check and let me know

Jamshaid

@Kalyan Sattaluri I can't find Add value to Audit Log in then: Add an action

Jamshaid

Screenshot from 2024-02-26 21-34-45.png

Welcome!

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

Quick Links

Find more posts tagged with

automation