Forums

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

Automation for sprintstart date and start date doesn't give the right date

Max October 2, 2025

I have an automation (see below) that sets the Start date to the Sprint.startDate whenever I change the value of a sprint. The automation works. But it changes to a day before. It does the same for the Sprint End and Due date. 

For example: My sprint starts the 2nd of October, I add the sprint, the Start date becomes the 1st of October. I've seen that this probably comes due to the fact that my timezone is different to the Jira time zone. But I just want it to set the value the same. How can I do that? 

Screenshot 2025-10-02 at 11.34.00.png

I've tried removing the .jqlDate, but then I get an error due to date formatting. Before that I used jiraDate, but that first introduced the date. 

 

3 answers

0 votes
Harpreet
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 2, 2025

Hello @Max ,

Welcome to the community..!

Could you please check below smart value for your use-case:

Start Date:


{{sprint.startDate.convertToTimeZone("Your/LocalTimeZone")}}
End Date:

{{sprint.endDate.convertToTimeZone("Your/LocalTimeZone")}}

 

Replace "Your/LocalTimeZone" with the appropriate timezone, such as "America/New_York".

0 votes
Bill Sheboy
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 Leaders.
October 2, 2025

Hi @Max 

First thing, the Sprint field in work items is a list of values.  Thus when a work item has carried over into other sprints, the expression you use could lead to a list of date values.  The fix for that is using the list function max to get the latest one, for example:

{{issue.sprint.startDate.max.jiraDate}}

 

Next for your actual question, I recall several defects in the public backlog for this symptom related to the Start Date and Due Date fields are date type while the Sprint's Start Date and End Date are date / time type (leading to challenges with conversion and time zones) when using automatic sprint durations

The only workarounds I remember were to explicitly set your Sprint values rather than the automatic values, ensuring they not near the date / time boundaries by picking the date exactly.

 

Kind regards,
Bill

0 votes
Christos Markoulatos
Community Champion
October 2, 2025

Hey @Max 

I have a suspicion that this is a time zone mismatchJira stores dates in UTC, and jqDate may not apply time zone correction for your local time zone.

Try using jiraDate instead of jqDate:

{{issue.Sprint.startDate.jiraDate}}
{{issue.Sprint.endDate.jiraDate}}

Hope tis helps and let me know if it worked!

Max October 2, 2025

Hi! I just tested it and it doesn't seem to work. I still get the date of the day before. 

Christos Markoulatos
Community Champion
October 2, 2025

It appears we need to hard code the time zone as @Harpreet  says, try it and let us know!

Suggest an answer

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

Atlassian Community Events