Dear Atlassian Automation Community,
I have created the below automation to Update Tasks Start and End Dates according to Sprint Dates -
To update the dates i am using the below -
The problem i am having it that in some cases the sprint date on the board show one thing -
While the dates i see on the Task are shifted by one day -
I know that this has something to do with the default Time value defined in the Sprint (E.g. 12:00 AM) as when I set it to 01:00 PM it gives the correct/expected date.
Any thoughts how can i get the Date without being influenced by the Time value defined in the sprint ?
In my opinion, this is a long standing behavior / problem with the sprint date / time values, and is related to both the automated selection of the "start of day time" and time zones, and then putting those into a date field (rather than a date / time field).
I hypothesize the feature is to support teams who actually end a sprint at 2pm and immediately begin the next one. Rather than end at Midnight and begin at 12:01am! :^)
For everyone else who starts a sprint on day-X, ends on day-Y, and begins the next one on day-Y + 1, a possible workaround is to try adding 12 hours before grabbing the values:
{{issue.sprint.startDate.max.plusHours(12).jiraDate}}
Kind regards,
Bill
Thank you @Bill Sheboy 🙏🏼
Like the idea 👌🏼
Decided to use "pluseHours(6)" just to be on the safe side not to get to the other side of the day in case the sprint is created mid day.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.