sprint.endDate.jiraDate wrong date returned

Marcel Reinieren

Since a while my automations fail on the following:

 

A comparison running on the last day of the sprint does this:

 

sprint.endDate.jiraDate equals now.jiraDate

 

My current sprint says: Projected end date: 23-09-2024

Smart value testing on sprint.endDate.jiraDate gives: 22-09-2024

Nothing has changed... Why is the smart value not giving me the same info anymore as shown on the sprint itself? (There's no time involved in the smart value; and it happens at arround 10:00 in the morning)

We use jira cloud.

(When I built the automation last year, it worked flawless)

Cristian0791

Hi Marcel,

It could be one of the following scenarios:

Time Zone Differences: JIra Cloud uses UTC internally for date and time operations. Even though you're comparing dates without times, time zones might be causing the mismatch. If your Jira instance or your user's profile settings have a different time zone than UTC, the now.jiraDate might be calculated in a different time zone, causing it to differ by a day.

Automation Timing: Since the issue happens around 10:00 AM, it could be that Jira calculates dates based on a cutoff time (e.g., midnight UTC). If your local time is ahead of UTC, this might result in a mismatch when the now.jiraDate is evaluated.

 

Hope this helps.