I work on project management templet as all our projects are epic in one project my team add daily comments for their task, I want to send a daily email to the supervisor containing each comment added on this day
the email should contain
- team member name
- issue summary
- comments
Hi @Amr Selem
I believe that is possible with a rule, although it would require filtering the comments by each individual team member's user, account id; there is no ability to sort or group-by when parsing comments in an automation rule. Such a rule could use a scheduled trigger, JQL to gather the issues, and smart value, list filtering to parse the comments.
Using automation rules requires learning and experimentation. I recommend you try creating your rule to meet your needs.
If you run into challenges, please post an image of your complete rule, an image of the audit log details showing the rule execution, and explain what is not working as you expect. That will provide context for the community to offer suggestions.
To get you started on creating your rule, please refer to these documentation and example sources:
Kind regards,
Bill
Please show the audit log details for the rule execution. That may help explain what you are seeing.
What is the JQL you are using for your scheduled trigger? And have you tested the JQL outside of the rule to confirm it works as expected?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please select "Show more" to see the details of the rule execution.
Repeating my earlier question: what is the JQL you are using for your scheduled trigger? And have you tested the JQL outside of the rule to confirm it works as expected?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Your rule does not have any issues provided and so the email is empty.
To help solve this, what version of Jira are you using: Cloud, Server, or Data Center?
If you are using Jira Cloud or Data Center, you may use the lookup issues action with a JQL statement to return the issues. Please look here to learn more about using that action: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues
If you are using Jira Server, it does not have that action. Instead you may use the bulk-handling feature, and add a JQL statement to your trigger to return the issues. Please look here to learn more about using that feature of scheduled triggers: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please show the details of your scheduled trigger, including the JQL you are using.
In your email body, you are using the lookup issues smart value. But first you must use the lookup issues action or that smart value will not work.
{{#lookupIssues}}
{{#comments}}
Comment by: {{author.displayName}} at {{created}}
{{body}}
{{/}}
{{/}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A scheduled trigger can only use valid JQL, and that is not valid JQL. Let's return to the earlier question, as I am not explaining this well and your rule is not valid.
What is your Jira version: Cloud, Server, or Data Center?
After you have answered that question we can continue. If you do not know the answer, please pause and ask your Jira Site Admin for assistance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information.
Here are 3 specific steps for you to try. Please perform them in the order shown.
If these steps do not help you, I believe you have skipped one or more of the things I have suggested. Please re-read them, and then try again.
If that still does not help, please work with your Jira Site Admin to submit a ticket to Atlassian Support for assistance: https://support.atlassian.com/contact/#/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.