Envrionment
Setup
Bug workflow create transition post functions
Addition Issue actions for step 2 above
import com.atlassian.jira.issue.Issue Issue issue = issue String issueKey = sourceIssue.getKey() issue.summary = "SLA | " + issueKey
Description
We have our Bug workflow auto-creating a "Team SLA" sub-task upon creation of the Bug. It uses the built in "Create Sub-Task" post function supplied by the Script Runner plugin. The Bug workflow is configured to fire a 'Create Issue' event. The "Team SLA" workflow is configured to fire a 'Generic Event' for the 'Create' transition in its workflow.
Problem
We receive 2 e-mail notifications. Once for the create of the 'Bug' which is as expected. But we receive a 2nd notification for the "Team SLA" from saying it was 'Assigned' eventhough there is no apparent assign event going on.
Questions
How can I stop it from generating the e-mail for the sub-task? Is the create subtask built in script firing the 'Assign' event internally?
Hello,
Sorry for the late reply!
What are you using to send emails (a listener, a post function, etc.)?
Could you please send me the condition for your custom email?
Jenna
I'm just using post functions to send e-mails. The post function fires a 'Generic Event' and the notification scheme for the project is configured to send no e-mail for a 'Generic Event'. There is no other e-mail handler configured.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, I think I understand now.
I believe that when you create a subtask it fires an 'Assign' event to assign it to your parent issue.
You probably need to set up something in your notification scheme that would ignore that 'Assign' event, if you don't have it already.
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.