ACP-100 key terms

A named set of users and groups defined per project, used by schemes and permissions so membership can vary between projects without changing global groups.

A reusable set of permission grants that maps each permission, such as Browse Projects or Assign Issues, to users, groups, roles, or the reporter.

A configuration that defines security levels and which users or roles may view issues assigned to each level, restricting visibility below project browse permission.

A global collection of user accounts managed in the user directory, usable across all projects for permissions, notifications, and sharing.

The user designated as administrator of a single project, often granted administrative permissions through the Administrators role in the permission scheme.

A mapping that controls which issue types are available in a project and which one is the default for new issues.

A set of rules per field determining whether it is visible, required, or optional, applied to issue types through a field configuration scheme.

An association of issue types to field configurations within a project, letting different issue types show or require different fields.

A mapping of issue operations, such as create, edit, and view, to specific screens that control which fields appear during each operation.

A project-level association that assigns a screen scheme to each issue type, so different issue types present different fields on create and edit.

A scope for a custom field that determines which projects and issue types use a given set of options, defaults, and description text.

An administrator-defined field added to issues, with a chosen type such as select list, date, or user picker, configured through contexts and screens.

A project-level mapping that assigns a workflow to each issue type, determining which statuses and transitions apply.

A defined set of statuses and the transitions between them, including conditions, validators, and post functions that govern issue lifecycle.

A directed link between two statuses in a workflow that a user triggers, optionally gated by conditions and validators and followed by post functions.

A rule evaluated before a transition is offered that hides or blocks the transition unless criteria such as permission or field value are met.

A check run when a user submits a transition that blocks the change unless input satisfies the rule, such as a required field value.

An automated action executed during a transition, such as setting a field, assigning the issue, or adding a comment, run in a defined order.

A transition available from any status in a workflow, commonly used for actions like closing or reopening an issue regardless of current state.

A trigger-based rule in Jira Automation that evaluates conditions and performs actions on issues, such as editing fields or sending notifications.

A reusable configuration that decides which events, such as issue created or commented, send email to which users, groups, or roles.

A system occurrence such as issue created, updated, or transitioned that can trigger notifications or automation rules.

A saved JQL query that can be shared with users or groups and reused by dashboards, reports, and subscriptions.

Jira Query Language, a structured text syntax for searching issues by fields, functions, operators, and keywords such as ORDER BY.

A configurable page of gadgets that displays saved filters, charts, and statistics, shareable with users and groups.

A dashboard component such as a pie chart, filter results, or activity stream that visualizes data from a source like a saved filter.

A saved search whose visibility is granted to specific users, groups, or everyone, enabling others to use it in dashboards and boards.

A setting that controls whether a user can sign in to Jira, Confluence, or other products, independent of project permissions.

A connected source of user and group data, such as internal Jira management or LDAP, that Jira queries for authentication and membership.

A preset bundle of schemes, workflows, and issue types used to create a project with sensible defaults for a team type.

The practice of reusing one scheme across multiple projects, so a single edit affects every project associated with it.

A label grouping projects for organization and filtering in project directories and some reports; it does not grant permissions.

A third-party add-on installed by an administrator to extend Jira with features such as reporting, field types, or integrations.

Jira's HTTP interface for reading and writing issues, projects, and configuration programmatically, used by integrations and scripts.

An outbound HTTP callback configured to notify an external system when specified Jira events occur, carrying a JSON payload.

A migration method that loads issues from a comma-separated file, mapping columns to fields and optionally creating users and projects.

The security level value set on an individual issue that determines which users can see it under the project's issue security scheme.