-
Suggestion
-
Resolution: Unresolved
-
828
-
33
-
When managing multiple teams and boards, it is impractical to manually update each sprint and start/end them individually. It would be much nicer if we could have the following features included in the future;
- The ability to add start and end dates to future sprints.
- The ability to select to automatically start and end sprints based on those dates on a Project-basis (wherever the sprint is housed).
- is duplicated by
-
- Closed
- is related to
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
[JRACLOUD-90921] As a Scrum Master, I'd like the ability to automatically start and stop sprints based on the dates I've entered.
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.
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?
This should be part of a core set of features. Why having someone to cut off the sprint manually at odd hours?
When using Jira Scrum/Kanban in a production and operations environment, this makes it easier to make sure that things are cropped in time and allow for the auto-roll forward of non-resolved (completed) assignments.
Now, this has a potential issue when some SubTasks might be closed but the Story is not (bad human discipline) and then the closing of the active/current Sprint is denied (I have experienced that and it makes sense but it will cause issues in auto-closing).
any news on this? seems like a quick win if this is already available in server/data center
Hi,
Sprint automation for Jira is a community-driven solution that solves this problem. Please check it out at https://marketplace.atlassian.com/1225720.
Try it free for one month, and please give us feedback about features, functionality, and pricing.
Happy to support the community!
Jerry
This feature will be really useful. Please add this one soon. Love to use Jira. Thank you for an amazing product. 
Keep up the great work.
I couldn't have written the ticket and scenario better myself. I've up-voted, I'm adding +1, and also Please. Thank you.
Hey Jira, I think this feature request has been open for long enough with plenty of interest shown...
Development effort VS value for clients is obvious...
Please schedule this for development.
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.