Issue Summary:
I’m encountering a situation in Jira where start and end dates on issues revert to old values immediately after manual change, despite no recent updates to automations, workflows, or permissions.
I encountered a similar scenario where changes to custom fields would revert unexpectedly. It turned out that there was an overlooked script running in the background which kept reapplying a preset configuration. Even though the workflow and automations seemed correct at first glance, a detailed audit of scheduled tasks and legacy custom fields revealed the issue. I had to disable the problematic script in order to allow manual updates to persist. My advice is to thoroughly review any integrations or background jobs that might interfere, even if they aren’t directly visible in the workflow settings.
Based on my experience managing similar issues in JIRA, I recommend focusing on checking for any hidden automation routines that might be automatically reverting changes. In my case, I discovered that a backend integration, not immediately visible within the standard JIRA settings, was resetting field values using a preset configuration. A thorough audit of all connected systems even beyond standard workflows and automation tasks eventually identified an old scheduled process running in the background. Once that process was identified and adjusted, manual updates retained their values as expected.
hey folks, had a similar issue. i later found tht an old integration job (forgot to disable after a migration) was trigering old dates. maybe a misconfigured script or glitch in a backend sync. worth double-checking any custom plugins.