We have a requirement for an alert to be triggered that will send an email when any active sprint is added to, which will cause scope change.
I do not know how to accomplish this.
This would be useful for us to. We have a problem whereby changes are being made to the sprint once it's in progress. To help get out of this habit, it would be really useful to have an email alert sent to the team every time this happens, so we can discuss why it's happening and find ways to improve our process.
Not hugely sure, but I can see a couple of possibilities:
Let us know if you come up with anything.
I don't really know how to do that. I have tried to use 'addedAfterSprintStart' already and every time I have tried it comes up with being unable to find that particular JQL function. As well as this I don't know how to write a query that will show if the sprint field has changed.
I have searched for an answer to this in Jira Cloud and finally decided to accomplish this outside fo Jira. I have all updates emailing me, which includes when the sprint value changes. I then created a rule in Outlook to label those emails differently so they jump out in the sea of Jira emails I am receiving now. Not ideal but it's effective and that's all I care about at this point. Hopefully Jira added this in the future but they seem to have their hands full atm.
Sure thing @Adrian Pilgrim. Jira has an option under Notification Schemes to send notifications on the Issue Update event, I set this up to email me directly. These emails contain the the task and sprint value along with some other data depending on what actually was updated on the task. I then created a rule in Outlook the flag these emails when they arrive with a category of red. Now when someone updates a task to a new sprint I receive an email with a big red box on it. It jumps out on my outlook inbox making it easier to be aware of when this occurs.
I found a few tweaks since I started this process to help. I removed the ability to assign a sprint value when creating a JT. I found that some people would create a JT and enter into the sprint while we are mid sprint! Furthermore the Issue Created event emails in Jira do not include the sprint value for me to create any rules like above. By forcing users to first create the JT and then update it to the current sprint I gain vision of this.
I also found that the event Issue Updated gives me way more emails than I want. So I edited my initial rule to move anything not tagged with the category of red to a subfolder. Now only sprint change updates go to my inbox. The rest of the updates go to a subfolder that I check periodically.
All of this is workarounds for functionality that does not exist in Jira at this time. This is the best vision I have gained on sprint changes in Jira yet but it is not perfect by any means. Hope this helps!
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events