We set Target Start/End date with a script runner automation. Essentially Target/Start and end are being populated by another custom fields value.
When we view an issue's history the Target Start/End Date are 1 day behind in the values being set by the automation.
Is there a known bug pertaining to history? We don't understand why these dates are being shown incorrectly in the history. Is there something different about Target Start/End date that would cause this behavior.
EXAMPLE:
In Issue History :
Target Start: Original:08/26/2024 New:09/09/2024
Actual Value for Target Start 09/10/2024
Verify your timezone settings in your User Profile, as they may be configured to an incorrect location.
Hope this helps!
Best regards
Sam
If that is the case and it is set on GMT Time wouldn't it move the time ahead 6 hours ahead? the date is always one day earlier. The history should reflect the same value that is in the issue's target start/end date
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.