I have automation that when a form is submitted it creates a bunch of subtasks on the ticket and spams all of us jira agents on the project as well as floods our Teams channel. Is there a way to disable the notifications we get just for subtask creation?
I’m working in Jira Service Management (Cloud) and have an automation rule set up using Automation for Jira. Whenever a hardware request form is submitted, it creates multiple subtasks on the ticket to handle the request. This is triggering a flood of notifications—both emails to all Jira agents on the project and messages in our Microsoft Teams channel—which is overwhelming our team.
I’d like to disable notifications specifically for subtask creation (not other events like updates or comments) while keeping the automation intact. I’ve looked into notification schemes, but they seem to apply to all issue types, not just subtasks. I also checked the "Create issue" action in automation, but there’s no "Send notifications" option like there is for "Update issue." Someone suggested using the REST API with notify=none, but I’m not sure how to set that up or if there’s an easier way.
Is there a straightforward method to stop these subtask creation notifications (both email and Teams) without affecting other notifications? Any guidance or examples would be greatly appreciated!
Hello, Good day. One thing you can try is to use a separate workflow for sub-task issue type and then remove the post function "issue created" event. This will not trigger the event itself.
@Mohanraj Thangamuthu I tried to remove the Issue created post function but it is not enabled the remove action.
Are we talking about the number 3 right? it is not enabled for me. Can you explain how to do it please?
Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, number 3, edit the workflow and move the mouse cursor next to this post function, then you will get the remove option. After this publish the workflow to apply the changes. https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.