Jiira’s native audit logging does not capture file or attachment download activity in a detailed or user-traceable manner. Specifically, it does not record who downloaded a file (SSO ID or username), nor the exact date and time of the download.
The built-in audit logs are designed to track administrative, configuration, and security-related actions, such as permission changes, project updates, and system settings. End-user content access, including attachment downloads, falls outside the scope of these logs and is therefore not recorded.
In environments where Marketplace add-ons are not permitted, tracking file downloads requires analyzing application server or reverse-proxy access logs. This involves identifying HTTP requests to Jira’s attachment endpoints and correlating them with authenticated user sessions or SSO tokens. Achieving accurate user attribution typically demands custom scripting, log aggregation tools, and strong technical expertise, and may still have limitations due to caching or shared sessions.
Where add-ons are allowed, dedicated Jira plugins provide a more effective approach by directly capturing attachment access events along with user identity, timestamps, and file details, enabling reliable audit trails.
In summary, Jira does not natively support detailed file download auditing, log-based analysis is a complex workaround, and specialized add-ons remain the only practical solution for precise and reliable tracking.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.