Automation - email on wroklog not updated

[POOBALAN MUNUSAMY]

I want to generate email automation to report on resources who didn't update their respective worklog the previous day.  what i get is empty mail ( refer attachment - mail.png ). Any miss in the settings ?

[Trudy Claspill]

Hello @POOBALAN MUNUSAMY 

Your post tags indicate you are using Jira Cloud. Based on the graphics in your images you are actually using Jira Data Center.  Please share with us the version of Jira Data Center you are using. You can get the version number by clicking on the Help button (near your avatar in the upper right corner) and selecting the About option.

To provide advice on why your rule might not be working, can you provide a screen image showing the current state of your rule? Also provide the following information. 

What are the details of the Create Variable action?

What are the details of the Send Email action?

If you are trying to use the Variable you created in the Send Email action, that will not work. You are creating the Variable within a branch. As soon as the branch completes, the Variable ceases to exist. If you try to use that Variable outside of the branch you will get no data and no error.

[Bill Sheboy]

Hi @POOBALAN MUNUSAMY 

Yes, and...to the suggestions from Trudy:

Based upon your scenario and the branching limitations described by Trudy for the Created Variable, please instead consider:

• Remove the JQL from the trigger, and only use the schedule
• Use either the Lookup Issues action or a branch on JQL with the bulk-handling feature to gather the issues
• Test if any issues were found
• Then use either the {{lookupIssues}} or the plural {{issues}} smart value, depending upon which approach you used (the action or the branch) to send the email

Kind regards,
Bill

[POOBALAN MUNUSAMY]

Hi Trudy,

its v10.7.4 

[Trudy Claspill]

Thank you for that additional information @POOBALAN MUNUSAMY 

Are you still using the original rule you wrote, or did you modify it as suggested by @Bill Sheboy ?

If you modified it, please show us the new rule and show the details of each component of the rule.

If you are still using the original rule, note that you can't effectively use the variable created within the branch as content in the email that is generated outside the branch. The variable will cease to exist outside of the branch.

You must modify your rule, and I would recommend you make modifications as suggested by @Bill Sheboy .

[Duc Thang TRAN]

Hello @POOBALAN MUNUSAMY 

If I understand your need correctly: the automation finds all assigned standard tickets (no epic or subtask) without work logged today, retrieves all assignee users, and sends this list to a team lead?

An empty list may be caused by an incorrect variable in your automation or how you're using this variable in the send email action. Can you share screenshots of these elements?

Also, the branch  in your automation (for stories)  will take child issues if the scheduled JQL retrieves an epic, and will ignore other issues (which is not ideal for me).
​

Simplified Alternatives
Create a filter with your JQL ex :  worklogDate < startOfDay() AND statusCategory != done AND assignee is not EMPTY and issuetype in (yours issuetypes)

and subscribe to it for daily emails to avoid automation complexity.
​

If you prefer automation for personalized emails:

Use a scheduled trigger without JQL.

Add a "Lookup issues" action with your full JQL to get the list of tickets (the number of tickets depends on the "Lookup issues" configuration in your Data Center; default is 100).

Use smart values like {{lookupIssues.assignee.displayName.distinct.join(", ")}} in the email body.

Hope this can help :)

[POOBALAN MUNUSAMY]

Hi Tran,

Yes, my objective is to check worklog across stories & subtasks and send the report the following day to reporting manager

refer to attachment, this settings incorrect ?. for test purpose, i set it to every 6 mins. Ithe idea is I want report to be generated the following workday only before 10am and send the report to manager

[Duc Thang TRAN]

Hello @POOBALAN MUNUSAMY 

In the parentheses, list all issue types for your needs,

for example (Story, Enhancement, and all subtasks) -> 

worklogDate < startOfDay() AND statusCategory != done AND assignee is not EMPTY and (issuetype in (Story,Enhancement) or issuetype in subTaskIssueTypes())

For subscribe jql , you can take a look on this documentation (it for cloud but similar on data center ) https://support.atlassian.com/jira-software-cloud/docs/manage-filters/ 
For your variable, I don't think it will work. You can try via a Log action to test if your variable is correct.

[Sebastian Krzewiński]

Hi @POOBALAN MUNUSAMY 

What is actual output of your rule? Is it working partially or nothing is working?

Regards,

Seba

[POOBALAN MUNUSAMY]

Hi Seba, I don't receive the expected output.. just the following

The following team members have not updated their worklogs within the required period:

Please ask them to update their Jira worklogs as per process.

Thanks,
Jira Automatio

[POOBALAN MUNUSAMY]

Hi Tran,

Whichever way to achieve the objective( send report to mgr on worklog status), whether using JQL or scheduled trigger without JQL..I'm fine

refer to screenshot, issuetype refers to ?