Why does Jira push the end date of a 2-week sprint to 14 days after the inputted start date?

[Doug Brophy]

Why does Jira push the end date of a 2-week sprint to 14 days after the inputted start date? For example, when I enter 10/Sep/19 12:01am (starting Tues) in the Start Sprint screen, Jira puts 24/Sep/19 12:01am in the End Date field (grayed out/ cannot edit), when the Duration field is chosen as 2-weeks. I don't want the end date to show 24/Sep. The correct end date is Mon, 23/Sep/19 11:59pm. If I do Custom duration with the date/time I want, Jira shows 9 working days in the sprint. ???

[Ollie Guan · Accepted solution]

Hi @Doug Brophy ,

Do you mean the remaining working days in the sprint? The start time you have chosen is already at noon on the 10th, so it is less than 10 working days until the end.

[Doug Brophy]

No, I mean the working days in the sprint, in the "Start Sprint" screen when starting a sprint. You will only see the "Start Sprint" button in the Backlog view with each sprint that has been created. Thanks for your reply Ollie.

[Tomas Gustavsson]

Not sure if that is the same, but on every sprint the shall be an start and an end date. 

even if the end date is grayed out, at least i could change it, but i'm an admin on my instance so maybe you need to request for some change in the permission scheme. 

Jira seem to only add 10 working days, which i think is fair, because sprints can be started any day of the week.

Another way is to change the start date for the sprint to 2019-09-09 and the end date will be 2019-09-23.

If you would like to have some thing different please set duration to custom 

[Doug Brophy]

Yes thanks Tomas I tried and observed all those things. To me, a start date/time of Sep-10 at 12:01am with an end date/time of Sep-23 at 11:59pm is a full 2 weeks/ 14 calendar days or 10 working days. But Jira doesn't represent it like that. With those Custom dates/times, Jira says that is 9 working days. I just have to work with it. 

[Paul Kern]

I agree with Doug Brophy on how it ought to work -- this is a bit of a shortcoming by JIRA.

[Cari Jostad]

Agree, this is quite a shortcoming by JIRA. Sep-10 start and Sep-23 end is 10 working days, not 9 as JIRA reports it. By having JIRA state it's 9 days, that throws off the teams velocity, metrics are skewed.

The JIRA 2 week selection would mean that I have a rolling 2 week Sprint that never starts on the same day. that's not how sprints work.

Can this be addressed?

[Ian deBoisblanc]

Agreed. Really just makes the "2 week" setting totally useless since every time I create a new sprint it default starts one day later in the week

[Tomas Gustavsson · Accepted solution]

What is your end date for your sprint?

[Doug Brophy]

Mon Sept. 23 (end of day).

[Doug Brophy]

Thanks for your reply Tomas.

[christopher_griggs]

I think we have entered into yet another thing where people are making up their own ideas on how things should work. If you schedule something for every two weeks, any calendar, would you expect the next date to be one day short? No.... 

In steps what I think has clearly become a problem. If planning is every other week - like a 2 week spring, then that is the time between two sprints. A new sprint should start immediately after the close of another sprint. 

So what happened? Ceremonies are now meetings on people's calendar and checklists because they all got their certs, and they want to say that we'll end a sprint the day before we start another... and so they want their Ceremony... for Sprint Review or something to be done the day before. 

There's no 'starting a sprint' or 'stopping a sprint' ceremony. Jira has a way to use a calendar to 'start' and 'stop' a sprint. This isn't a ceremony. When you schedule your ceremony on your calendar is not the same as a sprint cycle. 

In the end, if you start a sprint on a Tuesday, two weeks from that day is Tuesday... not Monday, and NO calendar should ever work that way.