Sprint length shows 11 days excluding weekends in burndown in Jira free version. Should be 10days
Asked by Venkata Unnam:

Hi Team,

I am new to Jira and am using Jira free version to learn how the sprint planning works from India. I created backlogs and 2 week sprints but Sprint plan shows 11 days excluding week ends. More details below.

My First Sprint started at 19th July 2024 2.30AM and ends at 2nd Aug 2024 11.30PM. As per this, burndown shows 11days. Why 2nd Aug 2024 included in the 1st sprint?

same way 2nd sprint started at 2nd Aug 2024 at 2.30AM and ends at 16th Aug 2024 11.30PM.

Why 2nd August included in the 1st Sprint and 2nd Sprint?

why 16th Aug 2024 included in the 2nd sprint?

.......

Same problem for all sprints in Jira free version. Is this issue in Free version only or in licensed version as well or this way Jira works? Please clarify.

Thanks

Unnam


Answers:
author: Bill Sheboy
body: Hi [@Venkata Unnam](/t5/user/viewprofilepage/user-id/5548994) -- Welcome to the Atlassian Community!

The sprint date boundaries (start and end) are included in the range, and those dates you show do span 11 days.

Kind regards,  
Bill

comments: author: Venkata Unnam
body: Thanks [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) for your response.

To start sprint, I selected 2 weeks sprint. That means 10 working days by excluding week ends but for me when I start sprint, it shows 11 days including start (19th July 2024 2.30AM) and end (2nd Aug 2024 11.30PM) dates . Is this how Jira works or any thing different in trail and licensed version?

Why every sprint last day considering again in follow-up sprint 1st day also? What is the purpose of this?

In my original query example, Why 1st sprint last day 2nd Aug 2024 is consider in 2nd sprint 1s day as well?

My understanding is 2 weeks sprint means 10 working days. the 1st day initial 4hours use for sprint plan meeting and developers will work on 9 days and 10th day 2nd half go for sprint demo, retrospective and close the sprint. 11th day 1st half will start sprint plan meeting for 2nd sprint. Isn't it way the Jira works?

Can you please give bit more elaboration to understand?

Thanks

Venkata Unnam


author: Bill Sheboy
body: First thing, please post an image showing what you describe as the "Sprint plan shows 11 days excluding week ends". Thanks!

Next, I believe the duration selection of "2 weeks" counts from the start with **date / time** , and so it runs through to the same time for what appears to be the 11th business day: but it is effectively 10 full business days. To force the boundaries to be within 10 *calendar* business days, please use the custom duration and set the times manually.

Reviewing the date / time values you note for the sprint range, they do span more than 10 working days: 19 July **2:30 AM** to 2 August **11:30 PM**. To be within 10 days, the end time would also be 2:30 AM on 2 August.

I have seen suggestions to make this less confusing in Jira, but the ability to select the start time is the complication: some teams do actually finish at a specific hour on a specific day and start the next sprint one minute / hour later on the same day.


author: Venkata Unnam
body: Thanks for your clarification. Please find below screenshot for 11 days shows in burndown chart .

![Gadget Burndown chart.PNG](https://community.atlassian.com/t5/image/serverpage/image-id/337692iD1E25FB30781EBA0/image-size/large?v=v2&px=999 "Gadget Burndown chart.PNG")

Thanks

Venkata


author: Bill Sheboy
body: As you have selected date and time values which span 11 weekdays, the burndown chart shows 11 weekdays. When selecting sprints which span 10 weekdays (or using 2 weeks), the reports will show 10 weekdays.

I am unclear how else to explain this, so perhaps another community member will be able to help.


author: Venkata Unnam
body: Thanks Bill. Seems there was some glitch in Jira free version last few days but seems resolved now. Seems looks good now. Thank you very much for your help.


Tags: cloud

jira-cloud