Audit
Query the audit log of your JIRA account.
Table Specific Information
Select
The driver uses the Jira API to process some of the filters.
The driver processes other filters within the driver. You can turn off the client-side execution of the query by setting SupportEnhancedSQL to false.
For example, the following queries are processed server side:
SELECT * FROM Audit WHERE Filter = 'ab'
Columns
Name | Type | References | SupportedOperators | Platform | Description |
RecordId | Integer | Common | The Id of the audit record. | ||
Summary | String | Common | Summary of the change. | ||
RemoteAddress | String | Common | The remote address of the record. | ||
AuthorKey | String | Common | Key of the author that made the change. | ||
Created | Datetime | Common | Date on when the change was made. | ||
Category | String | Common | Category of the change. | ||
EventSource | String | Common | What triggered the event. | ||
Description | String | Common | Description of the change. | ||
ItemId | String | Common | Unique identifier of the object item. | ||
ItemName | String | Common | Name of the object item. | ||
ItemTypeName | String | Common | Typename of the object item. | ||
ItemParentId | String | Common | Identifier of the parent of the object item. | ||
ItemParentName | String | Common | Parent name of the object item. | ||
FieldName | String | Common | The name of the changed field. | ||
ChangedFrom | String | Common | The updated value. | ||
ChangedTo | String | Common | The previous value. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description | |
Filter | String | Containing a string in at least one field. For example, providing up will return all audit records where one or more fields contains words such as update. |