Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can you have JQL Branch Rule Use Issue Function

Steve Tedeschi
Contributor
April 17, 2025

I am trying to create an automation the identifies the number of issues and their Story Point sum that have been added / removed from a sprint; i.e., my JQL is

issueFunction in removedAfterSprintStart("{{boardName}}", {{sprintId}}) AND (labels is EMPTY or labels not in(Placeholder))
issueFunction in addedAfterSprintStart("{{boardName}}", {{sprintId}}) AND (labels is EMPTY or labels not in(Placeholder))

 

This is project-scope automation and, while the Board filter does include issues from a second project, I am only interested in the tickets in the same project
* Board filter includes issues in ProjectA and ProjectB
* Automation is in ProjectA and I am only interested in ProjectA issues

No results are returned when the automation fires based on a trigger (eg Sprint closed)

Results are returned when scheduled and manually triggered. This, unfortunately, means I need to update the sprintId variable and manually trigger at each sprint close.

 

Any thoughts why the JQL wouldn't return results when automatically triggered?

1 answer

0 votes
Trudy Claspill
Community Champion
April 17, 2025

Hello @Steve Tedeschi 

Can you provide screen images that show your entire rule?

And can you provide images of what is written in the rule's audit log when it executes?

 

Steve Tedeschi
Contributor
April 18, 2025

@Trudy Claspill Sure - please see attached

Jira Log.pngJira Rule.png

Trudy Claspill
Community Champion
April 18, 2025

Thank you for that additional information.

You said that your rule was triggered by an event like Sprint Closed, but the rule image you shared does not use that trigger. 

Can you share images of the rule when you use that trigger, and the output in the rule audit log when such a rule executes?

Also can you provide the details of the Create Variable actions, please?

I would also suggest that you should add Log actions to print into the rule audit log the value of each Variable that you created to confirm it has the value you think it should.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer