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 - link new issues on different parts of a rule

Ivan Donigevich_ow5vtz

Hello,

I have a working part of a rule where:

1. an issue is created

2. the branch "For the most recent created issue" creates another issue and links it to the one above.

I need to link an issue created in this branch to another issue too.

I tried the same approach when another issue is followed by the branch "For the most recent created issue" but didn't find a way to pass there issue key of an issue created before.

Using JQL looking for an issue with some custom field value doesn't pass it.

Appreciate any idea.

BR,

Ivan

Accepted answers

Kian Stack Mumo Systems

@Ivan Donigevich,

I'm not quite following exactly what you are trying to do, but I'd take a look at using the Create variable action.

You can use this to store a value which you can access later. So after creating an issue, perform the action

Screen Shot 2021-02-24 at 12.58.49 PM.png

You can then later access this variable using {{recentissuekey}}.

adrien miniere

Hi, I had a similar issue and helped myself at this contribution. I solved it the following way:

in the "create a new issue" action, I set the following values for the json object:

and it worked pretty well. In my case, the ITSAMPLE service project is a second project, external to the one, where the rule is executed, but on the same tenant. The issueKey smart value simply takes the value: " {{issue.key}} ". It retrieves the key of the subtask just created in the automation, so not the key value from the parent issue, which triggered the automation, but the key value of the last created subtask.

Regards

Adrien

All comments

Kian Stack Mumo Systems

@Ivan Donigevich,

I'm not quite following exactly what you are trying to do, but I'd take a look at using the Create variable action.

You can use this to store a value which you can access later. So after creating an issue, perform the action

Screen Shot 2021-02-24 at 12.58.49 PM.png

You can then later access this variable using {{recentissuekey}}.

Bill Sheboy

Hi @Ivan Donigevich

Yes, and... to the suggestion from @Kian Stack Mumo Systems

Create Variable has some limits for scoping, so if you create a variable inside of the branch it may not have a value elsewhere in the rule. As a work-around you may want to create the variable and assign it to {{createdIssue.key}} before you branch.

Please see this article for some "spirited conversation" on this topic:

https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Create-variable-New-component/ba-p/1448118

Best regards,

Bill

Ivan Donigevich_ow5vtz

Moved to reply section

Ivan Donigevich_ow5vtz

Kian, Bill,

Thank you for the prompt response.

I guess using the variable value should be for the 2nd linked issue via Editing Issue action in its Additional fields section where I can assign an issue key and a link type to sub fields of Linked Issue field in JSON.

Can you please suggest how these sub fields are named and the assignment would look like? Here I haven't found them.

BR,

Ivan

Bill Sheboy

Ivan, would you please post an image of your rule? That may provide some context for the community to help you on this next question? Thanks!

__Bill

Kian Stack Mumo Systems

@Ivan Donigevich,

I'm not quite sure that I'm understanding what you are asking. Perhaps a screenshot of the rule would be helpful.

Ivan Donigevich_ow5vtz

Bill,

The actions are that.

The long arrow shows extension of the rule, the blue one - what issues are to be linked, the short arrow - where I'm going to edit the most recent issue and what issue key with.

So here:

1. Story and 2 Tasks are created, then the Tasks are linked to the Story (the left part of rule)

2. The right part: Task is created and it is to be linked to the 2nd Task.

BR,

Ivan

Linking issues.png

Bill Sheboy

Thanks for that image of the rule.

Just to check, is this working as you expect? Branches run asychronously and so do not necessarily complete before the following steps, leading to timing issues in rule execution. The 3rd task you are creating is *outside* of the branch, and so it is unclear what the value of "most recently created issue" will be:

it could be nothing (no tasks created yet), or
it could be the first task created, or
it could be the second task created.

If all of the creates are within the branch (or outside of a branch) you can probably expect the steps occurring sequentially.

adrien miniere

Hi, I had a similar issue and helped myself at this contribution. I solved it the following way:

in the "create a new issue" action, I set the following values for the json object:

Regards

Adrien

Bill Sheboy

Hi @adrien miniere

Thanks for that information; it is interesting that it works now.

The REST API for the issue create supports adding one link at the time of issue create, but that did not work in automation rules just a few months ago. Instead rules needed two actions: create issue and then add the link. Looks like Atlassian fixed something :^)

Kind regards,
Bill

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

jira-cloud