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

Rule is executed successfully but no email sent - Status showed as 'NO ACTIONS PERFORMED'

Vijay Kumar_ln3ogr

Hi,

I have created an automation. The automation goes like this. When sprint is about to close in next two days, an email should be sent to all the team members whose user stories are still not complete. So, need to remind them saying, 'Hey guys, you need to close the stories, before the sprint ends.
For this I have created below automation. As you can see, JQL query is executed successfully, but NO email is sent to my mail IS with a details of user stories which are currently in 'Non-Done' status. Can you please help me with this?
You can see the 'Audit Log' as well.

Accepted answers

Bill Sheboy

Hi @Vijay Kumar -- Welcome to the Atlassian Community!

Do you have the bulk-handling option selected for your rule's trigger? https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html

If not, your rule will, iterate over multiple issues (potentially sending multiple emails)

And, if the issues have ever been in multiple sprints, the advanced compare condition will not work. The reason the condition will not work is the Sprint field is a list of values, and so {{sprint.endDate}} is a list of values, preventing the diff() function from working.

To do what you described as the need, the rule's trigger should use the bulk-handling option and the rule should use the plural {{issues}} smart value.

Then assuming your open / active sprint is the latest one, the date needed for the comparison would be:

{{issues.first.sprint.endDate.max}}

Then your email could again use the {{issues}} smart value to iterate over them for the notification:

{{#issues}}
* {{key}} -- {{summary}} -- {{assignee.displayName}}
{{/}}

Kind regards,
Bill

All comments

Trudy P Claspill

Hello @Vijay Kumar

Welcome to the Atlassian community.

Your post tags indicate you are using Jira Cloud, but the screen images indicate you are using Automation for Jira on Jira Server or Jira Data Center.

When you click on the Help button near your avatar and select About Jira, what information do you get? I'm asking because it will show you a verion number if you are using Jira Server or Jira Data Center, and I want to know what version you are using.

I suspect that the problem is your reference to sprint.endDate . I suggest that you use a Log action to print {{sprint.endDate}} to your rule execution log file to confirm it has the value you expect.

John Funk

Hi Vijay - Welcome to the Atlassian Community!

The rule is not executing the way you want because it is not passing on the Advance compare step. In other words, when it ran, it did not find a Sprint with an End Date exactly 6 days from now.

So, you need to make sure that you test with issues that you know are in a Sprint that has that exact end date 6 days from now. Another way to check is to look at a current sprint and calculate the number of days to the end date in your head. Then update the rule to change from 6 to that number and then run it again as a test.

Vijay Kumar_ln3ogr

Thank you so much Trudy for the reply & my apologies for the late reply.
Here you go for the JIRA version. See below. I also confirmed with JIRA team that, JIRA instance is hosted on CLOUD.
JIRA Version.PNG
Secondly, like the way you suggested, i did add 'print {{sprint.endDate}}' to log action. It gave me the same output as it did before. It didn't print the Sprint end date. Please see the screenshot below.

Rule execution after updating log action.PNG

Vijay Kumar_ln3ogr

hi John, Thanks so much for the reply and I appreciate.
Apologies for my inability to understand the suggestions you made. So let me ask again. When you say, I need to manually check which are all the issues has the end date 6 days from now. Should I check by taking individual issues and see whether that particular issue ends in 6 days? The reason I am asking is, we do have definitive start date and end date for a sprint. My understanding is that a sprint once started with definitive start date and end date, all the issues within that sprint are bound to have definitive start and end date and as we progress, the number of days on the sprint would be reducing. As an example, my current sprint will be ending in 4 days. Please see the screenshot below, No of days.png

Also you mentioned that, i need to first find current sprint and calculate the number of days to the end date. SO could you tell me what all the smart values i can leverage for this rule? In the meantime, i will also try from my end about these smart values.

Trudy P Claspill

I will circle back later with more suggestions for your rule.

I wanted to quick reply that while your Jira instance may be hosted in a Cloud provider, like AWS, that is not the same thing as using the "Jira Cloud" product. Jira Cloud is the Software-as-a-Service version of Jira which is hosted and maintained by Atlassian.

Based on the information in your Help screen you are using Jira Server or Jira Data Center v9.12.12. That is a "self-hosted" product. Your company downloaded the software and installed it themselves on a host that they manage (or that is managed for them by a service provider).

The Automation functionality available in the self-hosted product vs. the Jira Cloud product is a bit different, so it is important to know which product you are using and the version (if self-hosted) to provide relevant guidance.

Bill Sheboy

Hi @Vijay Kumar -- Welcome to the Atlassian Community!

Do you have the bulk-handling option selected for your rule's trigger? https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html

If not, your rule will, iterate over multiple issues (potentially sending multiple emails)

To do what you described as the need, the rule's trigger should use the bulk-handling option and the rule should use the plural {{issues}} smart value.

Then assuming your open / active sprint is the latest one, the date needed for the comparison would be:

{{issues.first.sprint.endDate.max}}

Then your email could again use the {{issues}} smart value to iterate over them for the notification:

{{#issues}}
* {{key}} -- {{summary}} -- {{assignee.displayName}}
{{/}}

Kind regards,
Bill

Trudy P Claspill

Also, you need to put the Log action before the Condition. Since the Condition is not passing none of the actions that come after it will be executed.

Vijay Kumar_ln3ogr

Hi Bill,

Thanks much for the reply. I think I have bulk-handling option selected. Please see below and correct me if I am wrong.

Also, at any point in time, we will have only one active sprint. That is two-week sprint. Issues are moved from one sprint to the other, if team was not able to complete the story in the current sprint.

Bulk Handling Option.PNG

Other components and values given for those are as below,
Other components.png

Bill Sheboy

In that case, please test your rule and let us know if it is working as expected.

Vijay Kumar_ln3ogr

Unfortunately, it's not working. As I see, JQL is validated, looks like condition is not meeting. Again, it's just a wild guess. Or it could be something else. Don't know. Very confused.

John Funk

Why don't you just look for Active Sprint?

Vijay Kumar_ln3ogr

Yes..at any point in time we have only one active sprint. I use following syntax,

{{issues.sprint.endDate.max.diff(now).days}}