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

Can you have JQL Branch Rule Use Issue Function

Steve Tedeschi

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?

Accepted answers

All comments

Trudy P Claspill

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

@Trudy P Claspill Sure - please see attached

Jira Log.png Jira Rule.png

Trudy P Claspill

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.

Steve Tedeschi

@Trudy P Claspill - Hoping I answer your questions....

Trigger: Yes, the original automation was triggered by the sprint close event. I originally thought it was a timing issue and switched it to be triggered by commenting on a specific issue (also easier to test / trigger the automation. Here is the original rule and log. You can see that search result was empty.
Variables: Variables are used so that the automation can easily be exported / imported into different projects, allowing us to change the project key, sprint event (issues added / removed from sprint), etc. They are used to build the JQL executed in the automation; i.e.,
- 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))
Log Values: I had been using email contents for this purpose; can switch to logging values.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-data-center

data-center