nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workflow changes history

Monika Frolova

How can I see the history of workflow changes? Not only the last action

Comments

Nic Brough -Adaptavist-

I am not sure what you are asking, so two answers:

If you are asking about the issues going through the workflow, then the changes are all recorded on the issue's history

If you are asking about the administrators making changes to the workflow, then no history of that is kept unless they choose to keep copies of each workflow

Thomas Deiler_db00h3

Dear @Monika Frolova,

when you change a workflow you can make a backup of the wf before taking the modified workflow "live".

But in this step, Jira doesn't save the history of the workflow. You can save it manually by storing the backups, but you will not see the differences.

What you could do, is to export the workflow as an XML and store it in a VCS like 'svn' or 'git'. Then with the 'diff' commands, you can see and track the changes (history).

If somebody else changes the workflow, you have an entry in the issue history - but without seeing what changed in detail.

Fixing this for one customer, I implemented the upper solution, so that everybody could see what happened.

Do you need more information?

So long

Thomas

Patrícia Fortunato Montenegro

Dear @Thomas Deiler what is that mean when we see

JIRA SA made changes?

The customer ask me Who is JIRA SA?

Nic Brough -Adaptavist-

It means you have a user labelled as JIRA SA - ask your administrators who they are. (The SA suggests to me "system admin" or even a database user, but I would not bet on that before talking to your admins)

Alexander Stern _ Shern Consulting OÜ

In Jira Cloud this is unfortunately not very straightforward.

You can see some information in the audit log, but it doesn’t give a clean, focused history of workflow changes — especially if you’re trying to understand what changed over time rather than just the latest update.

Because of that, many teams either document changes manually (for example in Confluence) or only investigate when something breaks, which isn’t ideal.

In practice the challenge is less about accessing the data, and more about having a clear, readable history of workflow changes.