Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,294,619
Community Members
 
Community Events
165
Community Groups

How to identify the author of a global status change in Jira

Alex Community Leader Aug 06, 2021

Hi Community!

 

I recently came across a situation from a client that ignited my curiosity and helped me learn something new that I would like to share with the community.

Client request

I see that the project workflow scheme has changed. There is now a "Budget Approved" status instead of the "Approved." Is this a bug, or is there a user that made this change? 

 

Can you imagine how many problems an "inoffensive" change in status name can cause in a Jira instance? Right of the bat, I can see dashboards and reports that use the status name on JQL's stopping to give the right results. But I am sure it does not stop here.

Analysis

Even though Jira prompts the alert - "This status is used in other workflows, editing it will affect them." - a naive Jira Administrator might skim the message and perform the change. And then the warm is already done.

alert.png

When prompted with this customer request, my instinct drove me to search for the root cause in the Audit Log. Surprisingly, I discovered that the Audit Log does not register global status changes (here is a suggestion JRASERVER-70388 under consideration). 

Since the Jira Administrator who executed this change did so for a reason, just renaming the status back to "Approved" would solve this incident and disrupt another workflow.

So here is my thought process to find who made the change and ensure that another workflow does not break. 

  1. Identify all workflows that use the now renamed "Budget Approved" status in JIRA_BASE_URL/secure/admin/ViewStatuses.jspa
  2. Investigate the Last modified column on JIRA_BASE_URL/secure/admin/workflows/ListWorkflows.jspa to find the date and user who did the lastest change on the workflows from step 1
  3. Filter the Author in the Audit Log with one user from step 2
  4. There might be many entries, so search for the workflow name from step 1 on the Affected object (s) page.
  5. If you don't find anything, repeat steps 3 to 4 for other users.
  6. After a couple of iterations, voila! 

audit.png

 

I can say that I got lucky that this change was executed as part of a workflow change. Therefore, Jira logged the statuses removed and added.

For a status change executed in JIRA_BASE_URL/secure/admin/ViewStatuses.jspa, there will not be any entry in the Audit Log. Let's vote for JRASERVER-70388 !

Conclusion

With this information in mind, I could reach out to the Jira Administrator to create a new status and ensure that both workflows will be working as expected by users.

I hope it could give some additional insights on troubleshooting, and if you have any other experience in troubleshooting this type of change please comment.

 

Cheers,

 

Alex

 

 

1 comment

Thanks, @Alex  And here is the link to the 17 year old Cloud ticket for this suggestion, if people want to watch/vote for it: https://jira.atlassian.com/browse/JRACLOUD-3157

We set up a webhook to push out logs and watch them in an external tool, just to track things which can age out of the Jira logs.

Best regards,
Bill

Like Alex likes this

Comment

Log in or Sign up to comment
TAGS

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