JIRA administrators can create custom Schemes to define unique sets of permissions for projects. Schemes in JIRA are configurations that allow administrators to control various aspects such as permissions, notification schemes, issue security, etc. They provide flexibility in defining specific configurations tailored to project requirements. Thus, option 3 is correct.

JIRA Service Desk distinguishes between request types and issue types by their respective purposes. Request types are used to categorize and manage incoming service requests, while issue types are used to classify tasks, incidents, and other work items within the system.

Some common types of reports that can be generated in JIRA include Burndown charts, Pie charts, Time tracking reports, and Issue statistics. Burndown charts visualize the progress of completing tasks over time, Pie charts display the distribution of issues by category, Time tracking reports show the time spent on tasks, and Issue statistics provide insights into issue status and trends. These reports help teams analyze project performance, identify areas for improvement, and make data-driven decisions.

Custom fields in JIRA are primarily used to enhance issue data by allowing users to capture specific information that is relevant to their project or organization. They enable users to customize JIRA to suit their unique requirements by adding fields such as text fields, dropdown lists, checkboxes, etc., to capture additional information beyond the default JIRA fields.

To link two issues in JIRA, you can use the "Link" option available in the issue menu. This allows you to establish a relationship between the two issues, such as "blocks", "is blocked by", "relates to", etc. Linking issues helps in managing dependencies and understanding the connections between different tasks or pieces of work.

The common file format used for exporting data from JIRA is CSV (Comma-Separated Values). This format allows easy manipulation of data in spreadsheet software like Excel, making it convenient for users to analyze and work with the exported data efficiently.

Workflows in JIRA consist of various states through which issues transition. These states are defined to control the flow of work effectively.

Swimlanes in Agile boards allow for the visual separation of work items based on specific categories. This helps teams to organize and prioritize their tasks effectively.

A Kanban board visually represents the flow of work by dividing it into columns representing different stages of the process. By limiting the number of tasks allowed in each column, it helps in visualizing work in progress (WIP) and encourages teams to focus on completing tasks before starting new ones, thereby improving efficiency and throughput.

The purpose of the "Sub-task" issue type in JIRA is to break down larger tasks or user stories into more manageable sub-components. Sub-tasks allow for better tracking and management of work by dividing complex tasks into smaller, more achievable pieces. This helps teams to organize and prioritize their work effectively, as well as allocate resources more efficiently.

Velocity is the most suitable Agile metric to focus on in this scenario. It measures the average amount of work completed per sprint and can help the team understand its historical performance and set realistic goals for future sprints. By tracking velocity, the team can identify trends, adapt its planning, and strive for continuous improvement in delivering committed story points.

In JIRA Automation, conditions are used to specify the circumstances under which a rule should be executed. These conditions can include criteria such as issue type, status, or custom field values. Triggers, on the other hand, initiate actions based on specific events. Filters are used to narrow down the scope of search results, and actions are the tasks performed automatically by rules.