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.

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.

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.

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.

An "issue" in JIRA refers to a task, bug, or any unit of work that needs to be tracked within the system. It can represent a task to be completed, a bug to be fixed, a feature to be developed, etc.

The correct option is "JQL Query." You can use JQL (JIRA Query Language) to construct a query that filters out unresolved issues in a specific project and of a certain issue type.

Automation in JIRA Service Desk can be leveraged through workflow triggers to automatically assign tasks, reducing manual effort and ensuring prompt handling. This helps in streamlining the request handling process by ensuring tasks are routed to the right individuals without delay.

The Plugin Manager component in JIRA is responsible for managing external integrations and plugins. It allows administrators to install, configure, and manage third-party plugins that extend JIRA's functionality. Plugins can provide additional features, integrations with other tools, or customizations tailored to specific business requirements. By managing plugins, the Plugin Manager helps enhance JIRA's capabilities and adapt it to the needs of different teams and organizations.

In JIRA workflows, a "transition" refers to the movement of an issue from one status to another within the workflow. It represents a change in the state of the issue, indicating progress or a change in its lifecycle. Transitions are defined in the workflow configuration and specify the conditions and actions required for the issue to move from one status to another. Understanding transitions is crucial for managing the flow of work and ensuring efficient issue resolution.

The default issue type in JIRA when you create a new project is usually "Task". Tasks represent pieces of work that need to be completed as part of a project. However, this default issue type can be customized based on the needs of the project or organization.

Structuring tasks using different issue types in JIRA offers several benefits. By using an "Epic" for the overarching feature, "Story" for high-level user requirements, and "Sub-tasks" for specific implementation tasks, you can achieve clear organization and tracking at different levels of granularity. This approach allows for better visibility into the progress of the feature and ensures that tasks are appropriately broken down for efficient execution.

Bulk Operations in JIRA are primarily used for performing actions on multiple issues simultaneously. This includes actions like transitioning multiple issues through workflow states, editing multiple issues' fields at once, moving multiple issues to a different project, and more.