In JIRA, a global permission refers to a set of permissions applied to all projects in the instance. These permissions typically include actions such as creating projects, administering users, and managing system configurations. Global permissions are managed by JIRA administrators and are crucial for maintaining security and access control across the entire JIRA instance.

Quick filters in Agile boards enable the creation of both static and dynamic criteria for filtering issues displayed on the board. This flexibility allows users to focus on specific subsets of issues based on their current needs.

In JIRA, a user represents an individual account, while a group is a collection of users. Users have their own set of permissions and can perform actions independently, whereas groups are used to assign permissions to multiple users collectively. Users can belong to multiple groups, allowing for flexible permission management.

Before initiating a restore process in JIRA, it's crucial to take certain precautions. Firstly, verify the integrity of the backup to ensure it's not corrupted. Secondly, ensure compatibility between the backup and the JIRA version to prevent any compatibility issues during restoration. Additionally, it's recommended to disable email notifications and stop JIRA services to prevent any interruptions during the restore process.

The key components of a JIRA Service Desk knowledge base include articles, categories, and labels. Articles contain the information and solutions for common issues, categories help in organizing articles effectively, and labels enable easy search and retrieval of relevant articles.

To reassign an issue to the correct team member in JIRA, the appropriate action is to use the "Assign" option. This allows the user to select the correct team member to whom the issue should be assigned. Therefore, the correct option is Assign.

A Burndown Chart is typically updated daily during a sprint. Daily updates allow the team to track progress, identify any impediments, and make necessary adjustments to ensure sprint goals are met.

JIRA Automation Rules are used primarily to automate repetitive tasks within a project. For example, you can create rules to automatically assign issues to specific team members based on certain conditions, or to trigger notifications when certain events occur. This helps streamline workflow and reduces manual effort.

The Burndown Chart in JIRA is specifically designed to track the progress of work during a sprint. It provides a visual representation of the work completed versus the work remaining over the duration of the sprint, allowing the team to assess their progress and make necessary adjustments to meet their sprint goals. The chart typically plots the ideal trend line (showing the projected completion based on the team's velocity) and the actual work completed, enabling teams to identify any deviations from the planned trajectory.

The correct option is Option 3: System Settings. A full system backup in JIRA encompasses crucial data such as issues, projects, attachments, and system settings. These settings are vital for restoring the system to a previous state.