We are using GreenHopper to plan our Sprints.
How can I ensure that developers don't get email notifications against Stories/Tickets in Jira unless that Story/Ticket is assigned to them and in the current Sprint?
Trying to eliminate a lot of noise generated when discussing tickets that are not immediately relevant for a given developer.
OK, so leaving the 'OnDemand' aspect aside....
Thats a great Idea, but how do you determine who the developers are? how do you know what the current sprint is, its possible to have more than one sprint active at any time (human nature).
I ask as JEMH can take over the project notification role from JIRA (even re-using the notification scheme) but filtration, thats something Ive not yet implemented, so Im looking for use cases...
You can only restrict notifications for each project by creating for each a different notification scheme.
Unfortunately the feature to restrict it per sprint does not exist yet. Though, we have created a new feature request to do so (GHS-11185). Please feel free to add your comments and vote for it to make it more noticeable to our developers. Also refer to Implementation of New Features Policy for more information on Atlassian's approach to the development of these improvements requests.
Please let us know if we can help you any further.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot