Hi Team,is there any changes in jira ,all of sudden project work flow changed in org came to default

[Abilash]

Hi Team,is there any changes in jira ,all of sudden project work flow changed in org came to default workflow,as checked no audit logs have worlflow changed any other

[Germán Morales _ Hiera]

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.

[Abilash]

The is in audit log showing,jira app done changes,this belong to workflow change task?
"data": {

  "type": "events",

  "id": "e7bb1270-daa2-41c7-9d47-12d7ea362bd4",

  "attributes": {

   "time": "2026-06-05T09:24:57.004Z",

   "action": "jira_field_configuration_scheme_created",

   "actor": {

    "id": "jira",

    "name": "Jira",

    "email": "Atlassian app",

    "picture": null,

    "links": {}

   },

   "context": [

    {

     "id": "2bc2ccde-c7ba-481a-abe9-4cc3aa3cae63",

     "type": "sites",

     "attributes": {

      "changedValues_associated_to_issue_type_s__from": "None",

      "changedValues_associated_to_issue_type_s__to": "All issue types",

      "objectItem_objectType": "CUSTOM_FIELD",

      "siteHostName": "https://.atlassian.net",

      "objectItem_objectName": "customfield_11375",

[Germán Morales _ Hiera]

Hi @Abilash, that log line isn't the workflow change. The action jira_field_configuration_scheme_created, with Jira itself as the actor, is what Jira generates automatically whenever a custom field is created: every new field gets a context (a field configuration scheme) made alongside it. Here it's for customfield_11375, being set to apply to all issue types. So it's a routine system event, not someone resetting your workflow, and it doesn't explain the project dropping to the default workflow. Atlassian describes that automatic behaviour here: Configure field contexts in your site

If the workflow genuinely reverted, use that entry's timestamp (2026-06-05, 09:24 UTC) as your anchor and look at everything in the audit log around that exact moment. A single operation, like creating a project from a shared configuration, a migration, or an app action, can fire several system events at once, so the workflow scheme change you're actually looking for may be sitting right next to this field one. Keep in mind too that Jira's native audit log doesn't record every field or scheme change, so a missing "workflow changed" entry isn't proof that nothing happened.

[Abilash]

Hi @Germán Morales _ Hiera ,Thanks for your response its helped a lot.