Does anyone know if it is possible to send only an email to a specific group containing an issue list containing key, summary and cost field for example?
I don't want the option to subscribe to the filter because the person can leave. I tried to use Jira automation, I was able to send an email with the list but the custom fields are not sent.
In JMWE I tried to use the schedule action because it allows to send periodically, but it sends an email for each issue and not a single email.
Working with your site admin, you could subscribe to a saved filter with a group. Then just edit the group membership as people join/leave. Please look here for information about how to do this: https://support.atlassian.com/jira-core-cloud/docs/work-with-search-results/#Workingwithsearchresults-subscribeSubscribetosearchresults
Best regards,
Bill
Hi Bill, Thank you for yor time.
I saw this option but as far as I have seen, the groups displayed are created in the global settings of the jira. This list that I need to create is by project. I would need something that I could create and leave a book for the project to change.
Do you know if there is a way to leave this being configured only within the project without changing global settings?
Best Regards,
Juliano
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi! I do not know how to subscribe at a project level with out of the box Jira. And I believe the subscribe-to-a-group permission is global scope.
An alternative at the project-scope is to use an automation rule to send desired notifications to a list of people you define, at the project level. Those rules may be scheduled (like a filter subscription) or triggered on other events, such as issue field changes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
At the American Academy of Family Physicians, siloed marketing teams faced delays and duplicate work. Kerrie Gottschalk shook things up by moving the department to Jira, streamlining processes, boosting visibility, and sparking stronger collaboration.
Read the story
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.