Hi, I want to setup a very simple Jira automation. * Trigger: sprint started * Condition: every issue in the sprint that has a linked issue of type 'relates to' * Action: transition linked issue (in other project) to PLANNED I have tried multiple approaches but keep getting 'component incompatible' errors. This is what I expect would work (but doesn't): And this works, but as soon as I change manual trigger to sprint started, it stops working. I confirmed by sending myself an email that Lookup issues returns the same list of issues before branching off: I cannot figure out why changing the trigger results in an incompatibility issue. Any help would be much appreciated, 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; } } }

On sprint start, transition linked issues (Jira Automation)

axl.verheul

Hi,

I want to setup a very simple Jira automation.

Trigger: sprint started
Condition: every issue in the sprint that has a linked issue of type 'relates to'
Action: transition linked issue (in other project) to PLANNED

I have tried multiple approaches but keep getting 'component incompatible' errors.

This is what I expect would work (but doesn't):

Screenshot 2024-08-12 at 16.30.47.jpg

And this works, but as soon as I change manual trigger to sprint started, it stops working. I confirmed by sending myself an email that Lookup issues returns the same list of issues before branching off:

Screenshot 2024-08-12 at 17.19.14.jpg

I cannot figure out why changing the trigger results in an incompatibility issue.

Any help would be much appreciated, thanks.

Accepted answers

Bill Sheboy

Hi @axl.verheul -- Welcome to the Atlassian Community!

That error message can be a bit confusing, and what it means is a rule step needs an issue and none is present.

For your rule triggered on Sprint Started, you want to access the issues in the sprint. And so normally the rule would branch to the issues in the sprint. But you also want to access the issue which are lined to those issues in the sprint, and branches cannot be nested.

One solution for this scenario could be:

Using Lookup Issues with JQL, gather issues in the sprint which have issues with a link type of "relates to"

project = yourProject
 AND sprint IN openSprints()
 AND issueType IN (Injection, Bug, Story)
 AND issueLinkType = "relates to" ORDER BY Key ASC

Create a variable, using list filtering to extract the linked issues from the lookup results: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 Let's name that variable varRelatedIssues

{{#lookupIssues}}{{#issuelinks}}{{#if(equals(type.name,"Relates"))}}{{inwardIssue.key}}{{outwardIssue.key}},{{/}}{{/}}{{/}}

Finally, use a branch on JQL, and cleaning up the variable to remove duplicates, and removing any issues from the lookup (which are currently in the sprint and happen to be cross-linked as "relates to")

key IN ( {{varRelatedIssues.substringBeforeLast(",").split(",").distinct.join(", ")}} )
 AND key NOT IN ( {{lookupIssues.key.join(", ")}} )

Kind regards,
Bill

All comments

Bill Sheboy

Hi @axl.verheul -- Welcome to the Atlassian Community!

That error message can be a bit confusing, and what it means is a rule step needs an issue and none is present.

One solution for this scenario could be:

Using Lookup Issues with JQL, gather issues in the sprint which have issues with a link type of "relates to"

project = yourProject
 AND sprint IN openSprints()
 AND issueType IN (Injection, Bug, Story)
 AND issueLinkType = "relates to" ORDER BY Key ASC

Create a variable, using list filtering to extract the linked issues from the lookup results: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 Let's name that variable varRelatedIssues

{{#lookupIssues}}{{#issuelinks}}{{#if(equals(type.name,"Relates"))}}{{inwardIssue.key}}{{outwardIssue.key}},{{/}}{{/}}{{/}}

Finally, use a branch on JQL, and cleaning up the variable to remove duplicates, and removing any issues from the lookup (which are currently in the sprint and happen to be cross-linked as "relates to")

key IN ( {{varRelatedIssues.substringBeforeLast(",").split(",").distinct.join(", ")}} )
 AND key NOT IN ( {{lookupIssues.key.join(", ")}} )

Kind regards,
Bill

axl.verheul

Hi Bill,

Thank you for your reply! I was only now able to work on it and test your suggestion.

I don't understand how to configure the last step.

The initial lookup works fine. I can send myself an email with all sprint issues (that's why I'm surprised by the component incompatibility error missing an input type, as my email action does recognise the input).
The 2nd lookup (with your code) also works.
I am not sure if the assignment of a smart variable works, because when I send myself an email for debugging purposes, the body is empty. But that could also have to do with how I iterate over the smart variable.
I am not sure how to branch off this? There is advanced branching (with another smart variable assignment) and branch rules / related issues.

Screenshot 2024-08-16 at 16.29.09.jpg

Screenshot 2024-08-16 at 16.38.46.jpg

^ I also tried (type.name,"relates to")

Screenshot 2024-08-16 at 16.40.10.jpg

Bill Sheboy

The JQL expression in the last step I described would be used with a Branch on JQL as you wanted to transition those issues to the Planned status.

Is that what you still want?

axl.verheul

Hi Bill,

I'm a bit lost as to how to implement the smart values.

The closest I have gotten is this:

Screenshot 2024-08-19 at 16.22.37.jpg

But looking at the audit log, it only works with 1 issue in the sprint. If multiple issues are present, the JQL query fails.

Screenshot 2024-08-19 at 16.13.29.jpg

It also seems the Transition is not performed against the linked issue. I have double-checked the destination status and it is there. I also found the numeric ID (10051) but can only enter the name from the dropdown.

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