You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Welcome to the Atlassian Community!
What do you mean by "scope creep feature"? There is nothing described as that in Jira, and "scope creep" is not something you would implement into an issue tracker, it's more of a report on what your users are doing to move the goalposts on your project.
what i want is :--
After sprint gets started this automation should work and it should be able to count all Storypoint which got added in the sprint after sprint started and removed after sprint got started and when the sprint got closed it gives summary of the story point added and story point removed from the sprint.
Please help me how i can achieve this .
The sprint reports already do that, reporting on points added to or removed from a sprint.
If you want to see the report in other places, you will need to set up something that can extract and display it. Automation probably can't do it, because it works with issues, not reports. So the next question is where you want the scope-creep report to appear?
Ok, but when? What exactly is the event you want to trigger the report (email) on?
Every event where someone adds an issue to a sprint, removes an issue from a sprint, or changes the estimate on an issue in an active sprint? Or when a sprint is closed, so you can report on every scope change in one go? Or some other event?
for individual addition and deletion i already put automation in place(but deletion one not working properly) , now just want consolidated one mail which should trigger when sprint gets closed .
which should have:
SP added ( may be JIRA id also) along with SP of each issue
original SP when sprint started and now how many SP of work we have in sprint while closing the sprint.
Ok, so Automation has a "sprint completed" trigger, you can use that to create an email based on adding up the estimates on all the issues where "sprint = this one"
Automation does not have code, you'll need to work through your Automation rules a step at a time.
Adding to Nic's ideas about using the built-in Sprint Report...
It is difficult to accurately detect removal of issues from a sprint using an automation rule. It is better to use what Jira has already calculated for your team with the Sprint Report: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-sprint-report/
Please try sending the URL to the built-in Sprint Report when your sprint completes. That can easily be done with an automation rule. And you can dynamically create that URL based on the sprint which completed.
Next thing: using automation rules requires learning and experimentation. To get you started on creating your rule, please refer to these documentation and example sources:
Finally, the Atlassian Community is not a free labor pool to implement requests. If you are unable to build the rule yourself, please work with your team to hire a Jira administrator who can help you.