Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Log Entry for Change in the name of Status in a Workflow

Hi All,

      We had an interesting issue today. One of the admins had changed the Status in a workflow from 'Open' to 'Draft' (instead of creating a new one called 'Draft'). It has affected all projects across JIRA which use the status 'OPEN'. We reverted the changed and the issue got resolved. But strangely we could not find any log entry either in JIRA Audit Log or in atlassian-jira.log for the original change. When we reverted the change, we got this entry in atlassian-jira.log 

2018-07-12 11:48:00,802 http-nio-8081-exec-448 INFO vignesh 708x7730719x2 1dw5dl,,0:0:0:0:0:0:0:1 /secure/admin/workflows/PublishDraftWorkflow.jspa [c.a.jira.workflow.OSWorkflowManager] User 'vignesh(vignesh)' updated workflow 'Workflow_Name' at 'Thu Jul 12 11:48:00 EDT 2018'

Any idea where we can find the log entry when someone changes the name of status like 'OPEN' in a workflow? Is it captured in any other file?





The audit log in Jira is not comprehensive (unfortunately).  This is the issue related to your question, it is closed as duplicate, you just have to follow the linked issues:

You can plug some of the holes with this add-on:

It's frustrating that everything isn't logged, yet another reason to lock down Jira Admin permissions!

@Thad West Thanks for your response. I think its an important feature from an audit point of view to at least know who made the change.

I totally agree!

Something similar happened to me. I was able to pin down the "culprit" by looking at the dates the workflows were last edited, found the recent one where the new name made sense and looked at the name of the person it was last edited by. Not a solution of course, but it worked.


Log in or Sign up to comment

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you