ACP-420 flashcards
ACP-420 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Team-managed project
- A Jira Cloud project type whose issue types, workflow, fields, and board configuration live inside the project itself and cannot be shared with other projects.
- Company-managed project
- A project type that draws its issue types, workflow, fields, and permissions from shared schemes, so a scheme edit can affect every project using that scheme.
- Project key
- The short uppercase prefix chosen at project creation that begins every issue key in that project, for example ABC in ABC-123.
- Project category
- An optional grouping used to organize projects in the project directory; a project may belong to only one category at any given time.
- Issue type scheme
- A scheme that defines which issue types a company-managed project can use and which single issue type is preselected by default.
- Issue type hierarchy
- The three-level structure where Epic sits at level 1, standard issue types at level 0, and subtasks at level -1, with one configurable level above Epic in Cloud.
- Subtask issue type
- An issue type at hierarchy level -1 that can exist only as a child of a standard issue and can never itself be a parent.
- Default issue type
- The issue type selected automatically in the Create issue dialog, configured inside the issue type scheme associated with the project.
- Workflow draft
- An editable copy of a published workflow whose changes take effect only after the draft is published, and which can be discarded instead.
- Transition condition
- A rule evaluated before a workflow transition can be used, controlling which users are offered or permitted to execute it.
- Transition validator
- A rule that must pass for a transition to complete, commonly used to force a screen field to be filled before the status changes.
- Transition post function
- An automated step that runs after a transition completes, such as setting a field, adding a comment, or firing an event.
- Workflow scheme
- A mapping that assigns a workflow to each issue type in a company-managed project and names a default workflow for unmapped types.
- Field configuration
- A per-field setting list that determines whether each field is shown or hidden and required or optional for the issue types using it.
- Field configuration scheme
- A scheme that maps issue types to field configurations and defines one default configuration for issue types that have no explicit mapping.
- Screen scheme
- A scheme that maps the Create, Edit, and View operations to specific screens, which an issue type screen scheme then assigns to issue types.
- Custom field context
- The scope of a custom field, either global or limited to chosen projects and issue types, that determines where the field and its options apply.
- Permission scheme
- A named, shareable set of grants that decides what users, groups, project roles, and application roles may do inside a project.
- Issue security scheme
- A scheme defining security levels that restrict which users can view individual issues; it can only reduce visibility and never grants access.
- Browse Projects permission
- The baseline project permission; a user without it cannot see the project or its issues in the UI, filters, boards, or dashboards.
- Permission helper
- An administrative tool that takes a user and a permission and reports which grants allow it or which conditions block it.
- Project role
- A project-scoped membership list of users and groups that can be granted permissions through schemes, making access portable between projects.
- atlassian-addons-project-access
- A default project role that must include add-on and Automation users so those apps are allowed to read and modify issues in the project.
- Team-managed access roles
- The Administrator, Member, and Viewer roles used by team-managed projects to grant access to individuals or groups instead of classic project roles.
- Board filter
- The saved JQL filter that defines the universe of issues a board may display, which board columns then organize by status.
- Board sub-filter
- Additional JQL applied on top of a board filter that hides issues from the board view without changing the underlying saved filter.
- Swimlane
- A horizontal grouping of board cards by assignee, epic, story, project, or a custom JQL query, operating independently of board columns.
- Estimation statistic
- The board setting that selects story points, original time estimate, or issue count as the value used by velocity and burndown charts.
- Filter subscription
- A scheduled email delivery of a saved filter's results to chosen recipients, so they receive updates without opening Jira.
- Dashboard gadget
- A configurable report tile placed on a dashboard, such as Filter Results, Pie Chart, or Sprint Burndown, usually fed by a saved filter.
- Unpublished workflow draft
- The most frequent reason a workflow edit appears to do nothing: changes saved in a draft have no effect until the draft is published.
- Project trash
- The holding area where deleted Jira Cloud projects rest for 60 days, during which an administrator can restore them with their data intact.