Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Sprint was that it started with a different country's time zone.

Cristian Zuccalá
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 2, 2026
Sprint was that it started with a different country's time zone. This was corrected after starting Sprint with the correct time zone (GMT-3), but when we started Sprint it was in Spain (GMT+2).

imagen (12).png 

2 answers

0 votes
Gabriela
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 5, 2026

Hi @Cristian Zuccalá, welcome to the community. Changing the timezone didn't actually alter your sprint. Jira stores the start and end as a UTC instant, so switching from GMT+2 to GMT-3 only re-rendered that same moment in the new timezone; the sprint data is untouched, just the shown times moved by the 5-hour offset. If the displayed dates now look wrong and you want them corrected, open the sprint's ••• menu in the Backlog and choose Edit sprint, set the right start/end date and time, then Update. That works while the sprint is active; once a sprint is completed only its name and goal stay editable. Best, Gabriela

0 votes
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 2, 2026

Hi @Cristian Zuccalá

Welcome to the Atlassian Community!

Just to clarify, are you experiencing incorrect sprint reports after changing the timezone, or are you asking whether changing the timezone affected the sprint itself?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events