Jira issues show due and start dates reverting to past values after manual updates. No new automations or workflow changes appear to trigger this error. Has anyone else seen this?
I have encountered a similar situation where issue dates unexpectedly reverted to previous values. In my case, it was due to a hidden automation that was not immediately obvious. I spent several days combing through the audit logs and discovered that an old script, meant to standardize date input, was mistakenly activated under specific conditions. Disabling this legacy behavior resolved the issue. It might help to check for any system scripts or custom event listeners that aren’t obvious in the current workflow settings. A meticulous review of your Jira configurations could uncover the root cause.
I encountered a similar issue where date fields reverted to unexpected values after manual updates. In my case, the problem was tied to outdated field configurations that weren’t synchronized across all integrations. While reviewing system settings, I discovered that one of the connectors used an older version of the mapping configuration, causing it to overwrite the dates during periodic updates. Reviewing every integration alongside your custom field settings helped identify the underlying misconfiguration. I recommend a thorough audit of any external systems and their date handling for consistency within Jira.
hey, i had this too. turns out there was an api miscall with our external sync tool, which mismatched date fields. rechecking the configuration cleared it up for me. maybe its worth a look over your integrations, yiu might find something.