It feels silly to have to vote for a feature that was part of Jira Server, but is absent in Jira Cloud, but whatever, vote submitted.  Please allow us to automate the start and end of sprints in Jira Cloud.  There's no reason to have to manually start a sprint when you're following a regular cadence.  

This should be included as a native function of the product.  Introducing additional complexity of 3rd-party integrations or self-support scripting doesn't make any sense from a customer service perspective.  This is not lot of development to produce.  The dates can already be set in the sprint and the only other function needed would be a simple switch to choose the steering of unresolved issues (push to next sprint, push to backlog).

As a competitive product on the market, these should be simple value additions to your customers.

This should absolutely be possible through automation. A core concept of accurate sprint tracking is closing it at a set time. I get countless requests every 2 weeks to "please wait" "just 5 more minutes" and this would go a long way to teaching the discipline to my team.

Need this feature parity with server, as I use both server and cloud.

Hello,

I am the founder of Divim. We received from our consulting clients the same request, and we implemented an app called [Sprint automation for Jira

Another alternative is using Script Runner, but it doesn't do this out of the box, and creating the right handling of incomplete issues can require a lot of knowledge. 

Thanks,
Jerry

it's been open for years.  Atlassian clearly is not working on it.

This seems to be gaining a lot of interest. Is Atlassian working on this request?

This is very much required. We are facing lot of issues because this feature is missing in JIRA.

Jira Team, this issue has 500+ upvotes, can you add this to your product roadmap please? 

+1