So i understand the point of the "close" issue email. However my users do not. I get comments such as "did you just do this now? i thought you did it days ago!" and other questions like "this notification means what?" and questions about what they should do with these emails.
Therefor i would like to suppress close notification emails. We don't need them at all. What is the most straightforward way of dealing with this, while still preserving the automation piece that does the actual closing the issue?
I would like something easy that scales with all issue types if possible, so i dont have to edit every single one.
Notification is connected with an event. If you modify the workflow and not trigger an event you would not send any notification. You could also modify Notification Scheme and decide who will receive it and when.
If i am interpreting this correctly, You are saying to remove the "generic event" step in the 'transition close' workflow.
If that works and has no negative repercussions elsewhere then that's and OK solution. Unfortunately i have to edit it for every request type but there are only 5 or 6 per site so not that big of a deal...
Only problem is that when i go to delete that step, the delete button is greyed out :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As you can see you are using Generic Even for this specific transition (not Issue Closed), so eather change it to Issue Closed (which is already empty) or remove people/groups/roles from notification scheme associated with Generic Event
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
well i haven't modified anything. this is all stock. Ill have to look into what you are saying here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah ok finally had some time to look at this. Yes they are all set to generic. That is from the factory, i did not change this. It makes sense to set them all to "issue closed" notification (project - Notifications).
i am wondering if the framwork for the event "issue closed" is all set up, why it wasnt set this way by default. I guess thats the only part confusing me here. I will set them all to "issue closed" on the closed transition and hopefully my problem goes away!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It happens when you create a workflow from scratch - Jira doesn't know what events you might want to fire, but it has to put something in, so it just picks "generic" for everything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @JiraYo,
change the notifications behaviour in the notification schemes. You find them in the Jira Administration:
<your Jira url>/secure/admin/ViewNotificationSchemes.jspa
Change the notification settings for "Issue Closed".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nope i already did that. I believe these emails are because the status has changed to close. so its a status update email which obv i still want for MOST status types!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is it possible that your users are watching the issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
negative. well the user is the "reporter" on the issue. I am a watcher and the assignee. She got the email. I may have got it, i just delete them.
i think its perfectly normal if the status changes to get an email, but the closed status update email is just useless for my users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, I saw, that you fire a "Generic Event" - then of course, you have to disable the "Generic Event" - Notifications
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But then, of course, you disable any notifications on a generic event. It might be better to fire an "Issue Closed" - Event if the issue is closed.
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.