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

Sprint Completed - JQL returns no results

Carlos Matta

Hello,

I have set up an automation rule (trigger Sprint Completed) to send an email listing all items added after the sprint began. When I manually test the rule, either before or after the sprint ends, the JQL functions correctly. However, when the rule is triggered automatically at the sprint completion, the JQL returns no results. Do you have any insights into why this might be happening or any potential workarounds?

The log message "Sprint ID {{sprint.id}}, Sprint Name {{sprint.name}}" returns the correct values both during testing and when the rule executes automatically (sprint completes), so the issue doesn't seem to be there.

The JQL used is: issueFunction in addedAfterSprintStart(<Board ID hardcoded>,{{sprint.id}})

This JQL is executed within a "Branch Rule" because some fields are otherwise inaccessible.

I hope this information is sufficient, but please let me know if anything is unclear. Thank you in advance.

Accepted answers

All comments

Trudy P Claspill

Hello @Carlos Matta

Context and structure are critical in debugging an automation rule. Can you please share with us screen images showing your entire automation rule?

You said the JQL is executed "within a branch". How are you executing that JQL? Are you using a Lookup Work Items action?

How are you determining that the JQL is getting no results? What step following the execution of that JQL is not giving your the results that you expect if the JQL found issues?

Stefan Salzl

Hi @Carlos Matta

as @Trudy P Claspill already mentioned it´s always helpful to add some more information/data to your question in order to see the whole situation.

Without having any of the details my best guess/first question would be if you the option is selected/deselected in your jql-branch that only issues will be taken into context that have been changed since last run of this rule (see screenshot).

furthermore:

did you set the smart value of sprint.id into quotation marks so it represents a string?

Best
Stefan

Carlos Matta

I am having issues with this interface (replying to all of you).... hope it works this time...

Hello, thank you both for your input. The rule functions perfectly when the trigger is set to "Manual". However, it does not work when the trigger type is "Sprint Complete" The logs display the correct {{}} values (highlighted in red in the screenshot). To address your questions:

I iterate through the results using #issues to construct the email body.

I can confirm that no results are being retrieved, as indicated by the Audit Log ("No related issues could be found") and the fact that the email is empty.

The {{sprint.id}} is used without quotes.

The option to execute only items since changed is NOT selected.

The query executes successfully in the JQL prompt UI and, as mentioned above, when running this script in manual mode the log shows all the Keys resulted from the JQL and the e-mail has all items expected.

Bill Sheboy

Hi @Carlos Matta

Adding the the suggestions from @Trudy P Claspill ...

You appear to be using Jira Server (or Data Center). Is that correct?

And if so, you note using the plural {{issues}} smart value. That is only available when using the bulk-handling feature of branches or scheduled triggers. Did you enable the option?

https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html

If not, I would expect any references to {{#issues}} ... {{/}} to produce empty results.

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

automation