To install a JIRA plugin or add-on, users typically navigate to the "Plugins" section of their JIRA instance. This section allows users to manage and install plugins, extending the functionality of their JIRA instance according to their specific needs.

"Gadgets" on a JIRA dashboard refer to the various visual elements or widgets that display specific information or metrics related to projects, teams, or issues. These gadgets can include charts, graphs, statistics, or lists, providing users with real-time insights into project status, progress, and performance. Gadgets are useful for reporting as they enable users to customize their dashboards with relevant metrics and data visualizations, making it easier to track key performance indicators, identify trends, and communicate project status to stakeholders effectively. By configuring gadgets on their dashboards, users can create personalized reporting tools tailored to their specific needs and preferences.

In JIRA, sub-tasks are created under parent issues, which can be either epics, stories, bugs, or other issue types depending on your project's configuration. The parent issue defines the context for the sub-task.

Burndown charts in JIRA visualize the amount of work remaining over time, providing insights into project progress and trends.

A typical backup in JIRA includes crucial components such as the database, attachments, configuration files, and indexes. These components collectively represent the essential data and configurations needed to restore JIRA to a functional state.

The main difference between a "system field" and a "custom field" in JIRA lies in their origin and flexibility. System fields are pre-defined by JIRA and cannot be modified, while custom fields are created by users to cater to specific requirements. System fields typically cover generic information like Priority and Summary, whereas custom fields are tailored to individual project needs, allowing users to capture specific data relevant to their workflows.

The correct option is "Contains." This operator is used to search for issues that contain a specific word or phrase in their summary or description. It is useful for filtering issues based on keywords or terms.

Issue Security Scheme in JIRA is used to control visibility, allowing administrators to specify who can view particular issues based on their role or group membership, ensuring sensitive information remains protected.

JIRA Automation provides a built-in scripting language called Groovy for creating custom automation rules. Groovy is a versatile scripting language that allows users to write powerful automation scripts within JIRA.

Issue Security Schemes: Issue Security Schemes in JIRA enable you to restrict access to specific issues based on user roles or groups. By configuring the appropriate issue security scheme, you can ensure that only authorized users have access to sensitive financial data, thus maintaining data confidentiality and security within the JIRA system.