ACP-420 key terms

A project type whose issue types, workflows, fields, screens, and permissions all come from administrator-managed shared schemes, giving central control and consistent configuration across many projects on the site.

A project type where the team changes its own issue types, workflow statuses, fields, and access inside the project; those settings stay isolated from other projects and are edited by project admins rather than site admins.

A starting blueprint chosen at project creation that pre-fills settings, issue types, and sometimes sample issues for a common way of working, such as Scrum, Kanban, or service management.

The short uppercase prefix, unique across the site, that starts every issue key in a project; it identifies the project in JQL, URLs, and integrations and cannot be changed casually.

The practice of attaching one configuration object, such as an issue type scheme or workflow scheme, to several projects so that a single edit applies to every project using it.

A classification of work in a project, such as Bug, Story, or Task, that determines which workflow, screens, and field rules an issue follows.

A named collection that lists the issue types available to a project and names one of them as the default offered on the create screen.

An issue type that must belong to a parent issue and cannot stand alone; subtasks split work into smaller pieces and use their own workflow and screens.

The task of moving issues to a different issue type scheme, which may require mapping old types to new ones and can change statuses, workflows, and screen layouts.

The ordered set of statuses an issue can hold plus the transitions between them, defining who may move an issue, when, and what automation runs on each move.

A mapping that assigns a workflow to each issue type in a project, plus a default workflow used for any type without its own assignment.

A one-directional link between two statuses that a user triggers to move an issue forward or back; it can carry conditions, validators, and post functions.

The position of an issue inside its workflow, such as To Do or In Progress, shown on boards and used in JQL and reports to track where work stands.

A rule on a transition that decides whether the transition is offered to a user at all, typically by checking permissions, project role, or a field value.

A check that must pass while a transition runs; if the user's input fails the check, the move is blocked and an error message is shown.

An automated step that runs after a transition succeeds, such as setting a field, adding a comment, or creating a subtask, executed in a defined order.

The process of switching a project to a different workflow scheme, during which Jira maps existing issues to the new workflows and flags any statuses needing manual mapping.

A field created by an administrator to capture information beyond the built-in fields, with a chosen type such as text, number, date, or select list.

A set of rules applied to a group of fields that decides, for each field, whether it is required, optional, or hidden and whether it can be edited.

A mapping that assigns a field configuration to each issue type in a project, so different issue types can require or hide different fields.

A layout of fields used during one operation, such as create, edit, or view; a screen decides which fields appear, while field configuration decides whether they are required.

A mapping that points each operation - create, edit, and view - at a particular screen, letting one issue type show different fields for different actions.

A mapping that assigns a screen scheme to each issue type in a project and supplies a default screen scheme for types without their own.

The scope of a custom field's settings, defining which projects and issue types see a given set of options and whether the field is shared globally.

A named set of permission grants that decides who can browse, create, edit, transition, or administer issues in a project.

A scheme that defines security levels and the users, groups, or roles allowed at each level, hiding issues from people who would otherwise see the project.

A named visibility tier in an issue security scheme; each issue carries one level, and only people granted that level can view it.

A named membership list defined per project that permission and security schemes can grant access to, so people can be added or removed without editing schemes.

A site-wide collection of user accounts managed centrally, used to grant application access, permissions, and role membership across many projects at once.

An agile view of the issues returned by a saved filter, arranged in columns by status and optionally in swimlanes, with backlog and sprint features for Scrum teams.

The ordered list of issues not yet started in a Scrum project, where the team ranks work and pulls items into a sprint.

A time-boxed period on a Scrum board with a start and end date, holding the issues the team commits to finish before it closes.

The saved JQL query that supplies the issues a board shows; editing the filter changes which issues appear on the board and in its backlog.

The field a board uses to size issues, such as story points or original estimate, which feeds velocity, burndown, and sprint reporting.

A saved JQL query that defines a reusable set of issues, used as a board's source, a dashboard gadget's input, or a list shared with a team.

Jira Query Language - the text syntax for searching issues by field, operator, function, and keyword, used in filters, boards, gadgets, and integrations.

A page of configurable gadgets that show filter results, charts, and reports, shared with individual users, groups, or everyone on the site.

A single tile on a dashboard that displays data such as a filter results list, pie chart, or sprint burndown, each configured with its own settings.

An administration tool that explains why a user does or does not have a given permission in a project, listing each grant that applies and each that fails.

A record of configuration changes and administrative activity on the site that shows who changed what and when, used to investigate unexpected behaviour.