ACP-100 flashcards
ACP-100 · 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.
- Company-managed project
- A project type that uses shared schemes (issue types, workflows, fields) configured by Jira administrators; changes to shared schemes affect all projects using them.
- Team-managed project
- A project type with independent, simplified configuration; project administrators control settings, and schemes are not shared across projects.
- Project key rules
- Must be 2–10 characters, start with an uppercase letter, and contain only uppercase letters and numbers; cannot be changed after project creation.
- Issue type scheme
- A scheme that defines which issue types are available in a project and which issue type is the default when none is selected.
- Field configuration scheme
- Maps issue types to field configurations, which control field visibility, requiredness, and renderer for each issue type.
- Screen scheme
- Maps operations (create, edit, view) to screens; a screen is an ordered collection of fields shown during that operation.
- Custom field context
- A configuration that limits a custom field to specific projects and issue types; a field can have multiple contexts with different options.
- Workflow transition
- A directed link between statuses that allows an issue to move; it can include conditions, validators, and post functions.
- Condition vs validator
- A condition controls whether a transition is visible; a validator controls whether the transition can execute and shows an error if it fails.
- Post function order
- Post functions run in sequence after a transition; the order matters because earlier functions can set values used by later ones.
- Global transition
- A transition available from any status in a workflow; often used for actions like Close or Reopen across the workflow.
- Workflow scheme
- Associates issue types with workflows; a project has exactly one workflow scheme, and each issue type maps to one workflow.
- Automation rule structure
- Consists of a trigger (event or schedule), optional conditions, and actions; rules can be global or scoped to a project.
- Automation trigger types
- Include issue created, field value changed, scheduled (cron), and incoming webhook; the trigger starts rule evaluation.
- Notification scheme
- Maps events (issue created, commented, transitioned) to recipients such as groups, project roles, users, or email addresses.
- Custom event
- A user-defined event that can be fired by a workflow post function and associated with a notification scheme to notify recipients.
- Automation audit log
- Records each automation rule execution, including trigger, conditions, actions, and errors; used for debugging rule behavior.
- Filter sharing
- A saved JQL filter can be private or shared with users, groups, projects, or everyone; sharing controls who can use it in gadgets.
- Dashboard gadget
- A configurable widget on a dashboard, such as Filter Results or Pie Chart; it often depends on a saved filter being shared.
- JQL currentUser()
- A JQL function that returns the currently logged-in user; used in filters like assignee = currentUser() to personalize results.
- Filter subscription
- A scheduled email of filter results, delivered daily, weekly, or monthly to specified recipients; requires a saved filter.
- Jira REST API
- HTTP-based API under /rest/api/2/ or /rest/api/3/; supports authentication via basic auth, OAuth, or personal access tokens.
- Outgoing webhook
- An HTTP POST sent to a configured URL when selected Jira events occur; used for real-time integration with external systems.
- Application link
- A trust configuration between Jira and another Atlassian or external application, enabling features like issue linking and user impersonation.
- CSV import requirements
- The CSV must include summary and issue type columns; project key must exist or be created; date and field mappings must match Jira configuration.
- XML backup scope
- An XML backup contains Jira data such as issues, users, and configurations, but does not include attachments; those must be copied separately.
- Global permission Jira Administrators
- Grants access to Jira administration functions; membership is typically via the jira-administrators group.
- Project role
- A project-specific role assigned to users or groups; used in permission schemes and notification schemes for that project.
- Browse Projects permission
- The project permission required to view issues; most other project permissions depend on it being granted.
- User directory order
- Directories are checked in order during authentication; the first directory that authenticates the user wins, affecting group and permission resolution.
- Permission helper
- A built-in tool that explains why a user does or does not have a specific permission in a project, showing granting and blocking factors.
- Project category
- A grouping of projects for organization and reporting; it does not grant permissions by itself but can be used in some schemes.