+1. I also want this feature.

+1

+1

+1

Would be highly apprechiated to have this feature!

+++1

+1! My team is struggling very badly with this issue!

Same here please. All users are spammed by these updates even though it isn't relevant for them.

Yes, please allow Jira users or admins to stop receiving emails when a sprint updates.

This would be a very helpful feature.

+1

This would be a very helpful feature!

+1

We totally agree with this suggestion.

Yesterday, we have just experienced JIRA bombs ourselves (thousand of notification emails to team members) when sprints were deleted.

Totally agree with this suggestion!

We have bi-monthly sprints with my team, and every time a sprint gets updated, my team gets "Jira bombed" (we've actually given it a name it's so annoying).

An enhanced setting to be able to disable sprint updates only would be useful.

Guys, this is really, really annoying, and this bug was filed 8+ years ago!  C'mon!  Fix it!

I 100% agree with this comment:

Changing sprints is such a benign update to a ticket that typically everyone agrees on in advance. It is very frustrating to potentially receive hundreds of emails just because issues are moved in and out of sprints in bulk via the Agile boards.

Jira's backlog must be crazy, this feature has been open since 24/Oct/2012 and still "gathering interest".

Consider implementing it please

+1 That would be a solid feature in Jira. Making these events available for the community would be much appreciated!

Cheers,

Onder

Snapbytes UK Team 

+1 doing monthly sprint, it's really annoying to receive tons of emails because of a sprint change.

I agree with everyone, there should be a sprint specific option in the notification scheme, it's kinda crazy there is no option currently.

Changing sprints is such a benign update to a ticket that typically everyone agrees on in advance.  It is very frustrating to potentially receive hundreds of emails just because issues are moved in and out of sprints in bulk via the Agile boards.

 We need this to get an event when Sprint dates are changed.

This would be immensely useful.

6 years and counting...

How many votes do we need in order to push this on the Product Roadmap? This functionality is very useful.

Considering that Agile is PART of Jira now. This seems like an obvious oversight that should be added.

Duplicate: JSWSERVER-10760

This would be a great change to the software, our team always jokes as to how many emails we get and how long it takes to actually send them...

Wow, this ticket has been here for 5 years...and nothing from Atlassian.  How do they still not have this?  

Please have an issue end date (or due date) be populated by the Sprint it's assigned to end date.

we want to tag a commit Bitbucket based on start of sprint.

This would be very useful.

It would be great to to have these trigger a workflow transition.

In our workflow we'd like to put all items that are in a sprint into TODO status when the sprint starts.

In JIRA 7.1 you can use webhooks for Agile board events - i.e. Sprint started, Sprint closed etc.
https://confluence.atlassian.com/jirasoftware/jira-software-7-1-x-release-notes-788728210.html#JIRASoftware7.1.xreleasenotes-webhooksWebhooksforAgileboards

+1 , please have Sprint started and Sprint closed events.

I would rephrase it as "Triggering Sprint Started & Sprint Completed events".
We need it for automating "jobs" related to sprints, not only for generating notifications.

Any updates here? This issue was requested 3 years ago and has many votes. Any chance of it getting resolved any time soon?

@mtokar I just linked this issue to another that appears to be asking for almost the same kind of functionality.

Please note that, as of JIRA Agile 6.3+, the act of starting a sprint no longer triggers "Issue Updated" events. This used to be the case in earlier versions of JIRA Agile, because the Sprint object was not created (and assigned to issues) until the time when the sprint was started.

In JIRA Agile 6.3+, Sprint objects are created when you add a new Future Sprint. Issue are assigned to Future Sprints and at that point the Issue Updated event is triggered.

So there is still a case for:

• Better handling of multiple email notifications - JRA-1369 best covers this
• Triggering of events when sprints are started - let's repurpose this issue to cover this request

Regards,
JIRA Agile team

This is a much needed feature. Hopefully it will get worked in an upcoming release...

Alternatively, you could provide users more granular control over the emails they receive. As a developer I want email in only two cases:
1. When someone comments on an issue I'm watching.
2. When an issue is assigned to me (and even this is unnecessary since I just look at the scrum board to see what I'm working on).
I don't need an email every time a project manager changes a field on an issue, but I don't see any way to filter these.

I'm on a fairly small team, and I went from 0 inbox this morning to 60 messages, due to a variety of cases that haven't been shipped in this sprint. This is a very negative experience - email notifications are very important when done right, and can simply get tuned out completely when not able to be managed correctly. Really hoping for this improvement, and soon.

sijarvis, we see it as a valid feature request however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

Regards,
JIRA Agile team

Would it be possible to have any feedback on whether this modification is likely to happen please?

I agree with Chris. I am working with a department transitioning to using JIRA and their number one complaint is JIRA sending too many emails. I have tuned the notification scheme way down but I can't fix the over abundance of emails for sprints. It is super annoying to send emails about every sprint change. Even changing the name of the sprint sends emails. I have spent two years convincing this department to try using JIRA for project management and collaboration. And if I don't find a way to turn down sprint emails my hard work may be for naught. Please fix Atlassian. This is really needed!

I agree with everyone else's comments on this issue. I just now converted over to JIRA Agile and was stunned to see 32 emails in my inbox highlighting the changes to the Sprint field. I can only imagine what my users will say when they arrive in the office tomorrow. This is a serious issue in my opinion!

This is more of an issue in the latest version as now emails are sent for every future sprint change while planning. The notifications can only be configured at an "Issue Updated" level. From our perspective a change to the description or fix version is more important than a planned sprint change and we would like to handle the notifications separately.

I would love if JIRA/GreenHopper had unique "Sprint Started" and "Sprint Ended" events for which Notifications could be configured on a per project basis. This would give me the ability to let all stakeholders know when a particular sprint has started or ended so I don't have to remember to send them that information manually, and generally give more transparency to our development processes.

Please! This causes a painful flood of email and causes our team to pay less attention to email updates, therefore missing the important updates.

We need this functionality as well. Thanks!

We'd also like to be able to control notifications on sprints separately from the "updated" action. It sounds like our situation is very similar to Tim's: we release fairly often and everyone's inboxes get flooded with these notifications.

This is very close to a blocker in our adoption of Greenhopper. As a project whose workflow is public, we prefer to minimize any non-critical emails to watchers on our tickets, and we consider the 'sprint' change to be much less important than a change to fixVersion for conveying scheduling.

We can work around this by starting the sprint when it contains only 1 issue and then bulk-adding all of the remaining issues, but that's a rather ugly hack and having the choice built into Greenhopper to not send emails would be fantastic.

Hi! We'd like to combine our Portfolio Kanban Board and our Scrum Board and it would be great to get a start sprint event to be able to set a new status for all sprint issues of a started sprint to move them into a new column on the Kanban board automatically. => Voted!

This is a major annoyance with our workflow, since we release fairly often (once a week), at which point 20+ emails flood everyone's inboxes.