I am trying to create a rule that checks wether certain fields are empty. This is to ensure Stories are ready before the Sprint Starts. The 4 fields that I want to check are: * story points * acceptane criteria * description * Assignee I have created my rule for one field as a test but I am not able to get any data in the log. This is my rule How can I check that for each story a field is empty or not?

You can handle it in the same rule with an entirely separate Lookup Issues action for that condition, followed by an IF to check that the lookup found results, followed by a Send Email action to send the information to the person of your choice. Since the Assignee is empty in that case, obviously you are going to have to explicitly identify a recipient.

I have tried this, but it is not working!! I am expecting 1 story which I know it has no assignee

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

Checking for empty fields within Lookup issues

Ponce de Leon, Eduardo

I am trying to create a rule that checks wether certain fields are empty. This is to ensure Stories are ready before the Sprint Starts.

The 4 fields that I want to check are:

story points
acceptane criteria
description
Assignee

I have created my rule for one field as a test but I am not able to get any data in the log.

This is my rule

2025-02-19 15_25_54-Clipboard.png

How can I check that for each story a field is empty or not?

Accepted answers

All comments

Trudy P Claspill

Hello @Ponce de Leon, Eduardo

Welcome to the Atlassian community.

What is the ultimate purpose of this rule? If you find an issue that is missing data what do you want the rule to do? There may be a better way to achieve your desired end goal.

In the interim, there is a simpler way to iterate through the list of issues returned by Lookup Issues. Rather than using an Advanced Branch, use a Related Issues branch.

Screenshot 2025-02-19 at 1.47.32 PM.png

Ponce de Leon, Eduardo

HI Trudy, Thank you for your response. The ultimate goal is to send an email to each assignee indicating that a field is missing.

I understand the iteration but will I be able to send 1 email to an assignee that has 3 stories with empty description field for example?

Trudy P Claspill

Do you want to send the assignee one email for issues where Description is empty, and another for issues where story points is empty, and a third for issues where Acceptance Criteria is empty? Or do want one email per assignee with all issues that have any one or more of the fields empty?

In your first example of your rule you hard-coded the Assignee for whom you are creating the list. Do you plan to generate these emails for a static set of possible Assignees, or does the list of Assignees have to be generated dynamically from the list of issues?

Ponce de Leon, Eduardo

Hi Trudy,

I want one email per assignee with all issues that have any one or more of the fields empty?

for testing purposes I hardcoded my name in there but as a reporter and the assignees are different, at the end the list of assignees will be generated dynamically from the list of issues.