In JIRA, "Project Roles" feature enables you to tailor roles based on project requirements, granting specific permissions to users within those roles.

Zapier is a popular integration tool used to connect JIRA with external applications, enabling seamless communication and automation between different tools.

The knowledge base in JIRA Service Desk provides a repository of common solutions to issues and frequently asked questions, enabling customers to find relevant answers and self-serve, reducing the need for direct support and improving customer satisfaction.

The correct option is "To filter issues based on specific criteria." Quick Filters allow users to easily narrow down the displayed issues on Agile boards by applying predefined filters. These filters help in focusing on relevant tasks.

In JIRA, an issue and its sub-task have a parent-child relationship. This means that a sub-task is a task that is part of a larger task, known as the parent issue. Sub-tasks are used to break down complex tasks into smaller, more manageable units of work.

JIRA can exchange both textual (such as issue details, comments) and non-textual data (such as attachments, screenshots) with other tools through integrations. This allows seamless communication and collaboration between JIRA and external systems.

The Atlassian Universal Plugin Manager (UPM) is responsible for managing and installing plugins and add-ons within JIRA. It provides administrators with a centralized interface to browse, install, update, and configure plugins, ensuring seamless integration and management of third-party extensions.

In JIRA, workflows can be associated with a specific project. This allows for customization and tailoring of workflows to the specific needs and processes of individual projects within an organization.

In Agile project management, a backlog refers to a prioritized list of work items or user stories that need to be completed during the project. It contains features, bug fixes, technical tasks, and other work items. The backlog serves as a repository for all potential work and is continuously refined and reprioritized throughout the project lifecycle. In JIRA, the backlog is often represented as a backlog board where teams can visualize and manage their work items.

The "jira-users" group in JIRA is significant because it includes all users with access to the JIRA instance. Users added to this group typically have basic permissions to interact with projects and issues within JIRA. This group is fundamental for granting initial access to new users and ensuring that they can start using JIRA effectively. It is not exclusive to administrators or users with specific license types; rather, it encompasses all users in the JIRA environment.