Documentation

Events Log

The Events Log is your unified audit trail for everything happening across Ticket Mate and your connected integrations.

Overview

Every significant action taken by a user, an automation rule, or an external integration (Jira/GitHub) is recorded here. The Events Log provides the transparency needed for debugging workflows and maintaining security compliance.

What's Tracked?

1. System Events

Integration Syncs: Success/failure of Jira and GitHub background syncs.
Security Updates: Changes to API keys, roles, or permissions.
User Management: Invitations, logins (if configured), and account changes.

2. Automation Events

Rule Triggers: When a rule matches conditions and starts executing.
Action Results: Detailed logs of what the automation actually changed in Jira.
Failure Errors: Stack traces and reasons for rule failures (e.g., Jira API 403).

3. Integration Webhooks

Jira Webhooks: Incoming updates from your Jira instance.
GitHub Webhooks: PR merges, commits, and comments.

Filtering & Search

The Events Log can be filtered to help you find exactly what you're looking for:

By Type: Filter by "System", "Automation", or "Webhooks".
By Severity: Look for "Error", "Warning", or "Info" levels.
By Date: View specific time ranges.
Search: Search by Ticket ID, User Name, or Rule Name.

Troubleshooting with Logs

If a Jira ticket didn't update as expected:

Copy the Jira Ticket ID (e.g., TM-123).
Filter the Events Log by this ID.
Look for "Automation Rule Execution" or "Jira Sync" events to see exactly what happened or why it failed.

Data Retention

Logs are typically retained for 30, 60, or 90 days depending on your plan. For longer retention, consider exporting logs or using our external logging integrations.