Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT remote actions

Cloud migration hub

Additional product info

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

On this page

The Audit log (JWT) tracks the key events of our app. Those events can be viewed on the corresponding page and helps you to diagnose issues that may occur when implementing and executing workflow rules. To view the full audit log you need to be a Jira System admin or to have a Jira Administrator global permission. 

Who created or updated a workflow rule? Why did the execution on my issue not work last time? Get insights into what your users or you did with Jira Workflow Toolbox using the Audit log (JWT)!



Location

You find the audit log as an item in the App menu:

or as an entry in the "Manage your apps" menu:

Events

With the Audit log (JWT), we track the creation or update of a workflow rule configuration as well as its execution. The log supports you by providing as much information as possible so that you understand what goes on behind the scenes. We distinguish between the following events:

EventDescription
CREATEDA workflow rule has been created
UPDATEDA workflow rule has been updated
SUCCESSA workflow rule has been executed successfully
NO ACTIONS PERFORMED The condition of a workflow rule was not fulfilled during execution
ERRORThe execution of a workflow rule was not successfull

Learn more about all the columns
ColumnDescription
DateTimestamp of the event
UserThe user who executed the event
IssueThe respective issue key (if applicable, e.g. when executing a post function during issue transition)
ContextName of the JWT workflow rule
EventSee description above
ActionsIn order to show more detailed infomation, clicking on the row or the "Show more" button opens the details


Detail view

Our mission is to build apps for admins by admins. We know that while troubleshooting you need any available and additional information, especially when drilling down an issue. For this reason we have created a detailed view for each event logged in the Audit log (JWT). Depending on the action performed, you can access the following insights with a single click.

Learn more about the detailed view
ColumnDescription
Workflow nameName of the workflow to which the rule belongs (not available for created/updated events) 
Transition nameName of the transition where the workflow rule is defined (not available for created/updated events) 
ContextName of the respective workflow rule
Rule IDThe internal ID of the rule
UserName and Atlassian accountId of the user who triggered the event
Run as userName and Atlassian accountId of the user who actually executed the workflow rule (not available for created/updated events) 
DescriptionDetailed information of the event, e.g. a Jira or JWT error message or the issue key which was created during execution of a "Create issue" 



Search

Having thousands of entries would be a horror without a search option. With our flexible infix search, you can search for what you are looking for. Simply enter your term in the search field, optionally specify the period within you would like to search, and you are good to go.

During the search, every column within the audit log is searched. If you like to look for all actions a specific user has performed, you have to enter the respectice Atlassian accountId which is shown in the detail view. If you like to search all executions of a specific workflow rule, simply search for its rule id within the text field. 


You can get the information about the rule id within the expanded workflow rule view at your workflow configuration.

Following the privacy requirements, we don't store clear text information about the users, but calculate the displayed information on-demand, requesting the Jira application. Given this, you can search for events triggered or run as a user by searching for the account id of the user you are interested in.

Limitations

For JWT conditions and validators, no success event is logged due to the nature of their execution outside of our app.

The audit log cannot distinguish between drafts and active workflows, so you cannot tell whether a created or updated workflow rule is not yet active. 

No "deleted" event can be shown, i.e. if a workflow rule is deleted Jira does not inform our app.

If you still have questions, feel free to refer to our support team.