Hi @Abilash, an Atlassian side change that silently resets workflows across an org is very unlikely. That would be an announced incident on their status page, not a quiet revert. And a missing audit entry doesn't rule a change out either, since Jira Cloud's audit log doesn't capture every configuration change. Three places are worth checking, roughly in this order:
- The full Jira audit log, not the project activity: Settings (gear) then System then Audit log, plus the organization log at admin.atlassian.com. A workflow scheme edited or reassigned by another admin shows up here even when the project's own view doesn't.
- The workflow scheme behind the project. In a company-managed project the workflow is applied through a shared scheme, so if someone edited that scheme or switched the project onto a different one, every project sharing it flips to default at the same time. Check Project settings then Workflows to see what's actually assigned.
- A recent plan or subscription change. On Free, or right after a trial ends or a downgrade, customisations can quietly drop off and that never appears as a workflow edit, so confirm nothing moved on the billing side: Explore Jira Cloud plans
One thing that changes where you look: if this is a team-managed project rather than company-managed, the workflow lives directly on the project, so you'd check and rebuild it there instead of chasing a scheme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.