I can understand the frustration here, and yes, we’re aware of the concerns around the recent changes to ticket statuses. From a technical perspective, this kind of issue can happen if an automation rule, workflow script, or bulk update job was triggered unintentionally. In many ticketing systems, status fields are tied to workflow automations and API calls, so even a small change in configuration can result in tickets being moved en masse.
The team is currently reviewing the audit logs and database change history to trace exactly when and how the status changes were applied. If it was an automation trigger, it will be paused and rolled back; if it was a configuration error, we’ll correct the workflow logic and restore the last known good statuses. For customers, this means we’ll be able to revert the affected tickets using the audit trail, ensuring data integrity without losing any updates.
Best discussion https://community.atlassian.com/ buy to let forums/forums/editpage/board-id/jira-questions/message-id/1151432
Going forward, we’ll also implement additional safeguards such as bulk-change confirmations, anomaly detection (to alert when a large number of tickets change in a short time), and stricter permission checks for automated jobs. This way, we can prevent unnecessary disruptions and keep ticket handling aligned with customer expectations.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.