Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,557,125
Community Members
 
Community Events
184
Community Groups

close sprint automatically through scrptirunner

Hi Team,

We have a specific requirement to close the sprint automatically based on the start date of the sprint defined.

For example the sprint start date is Nov 15, 2022 & Sprint end date is Dec 15, 2022 and the sprint has 4 user stories.

The sprint has to close automatically for 14 days of start date and the user stories which are not closed should move to backlog.

kindly help on how i can achieve this?

Thanks,

Tejaswini

 

1 answer

0 votes
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 28, 2022

Hi @Tejaswini 

Can I confirm the need here?

  • Sprints should close automatically 14 days after the start date
  • This is regardless of the end date - i.e if a Sprint is 4 weeks long, it should still close after 2 weeks?
  • Once a Sprint is closed, all incomplete issues should move to the backlog

Can I clarify why this is being done automatically, rather than coaching the teams to create 2 week Sprints, and close them at the correct time?

It would be good to understand the logic behind this need alongside the technical requirements :)

Ste

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events