1- User Action History :

The user action history feature allows Jira administrators to track and audit actions performed by users on files attached to the custom fields of the Attach File plugin. Supported actions include:

Upload: This action records when a user uploads a file to the custom field. It allows administrators to see when a file was added and by whom.
View: This action tracks when a user views a file attached to a custom field. It allows you to monitor users who have accessed the file viewer interface and who can also download the file.
Note: This feature is only available for PDF files.
Download: This action logs when a user downloads a file. It provides a record of when and by whom a file was retrieved from the system.
Archive : This action occurs when a file is archived. It allows administrators to know when files are stored for long-term retention or removed from active use..
Delete: This action is recorded when a user deletes a file. It tracks the removal of files, providing a trail for administrators to understand what files were deleted and by which user.

Administrators can view and filter this history on the User History page, with filters for action type, user, or execution date. Additionally, administrators can export the user history data from the table in CSV format.

Note: The information of the user who performed these historical actions is retrieved from the database of your Jira instance.

If a user is deleted, the record of their actions will remain in the database, but their profile information (name, surname, etc.) will not display correctly and will appear as "Unknown".

Note: If the user performs actions on a custom field of type attachment field on a creation screen, this action will be recorded in the history but without an issueKey or projectKey, because at that moment, the issue has not yet been created, and therefore, there is no issue key yet.

2- Automated Cleanup :

However, for organizations with a large number of users, the history can quickly generate hundreds or even thousands of new entries per day, which may burden the database.

To address this, a Scheduled task service has been implemented. Every day at 3:00 AM (GMT), the Scheduled task runs automatically to delete action history records older than 2 months (See documentation for configure duration Attachment Global Setting).

This helps to maintain a lightweight database while keeping relevant records.

Navigateur non pris en charge