ACP-620 flashcards
ACP-620 · 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.
- Global permission
- A site-wide capability such as Browse Users or Jira Administrators that is granted outside any project permission scheme and applies across the entire instance.
- Application access
- A per-user setting that grants access to Jira Core, Jira Software, or Jira Service Management; without it a user can authenticate but cannot use the product.
- Audit log
- A record of administrative configuration changes showing the actor, timestamp, and before and after values, used to trace who altered settings and when.
- Reindex requirement
- A full or background reindex is needed after changing a custom field searcher or JQL-relevant configuration so search results reflect the new definition.
- Project role
- A per-project membership container that can hold groups, users, or directory groups, and is the preferred target for permission and notification scheme grants.
- Shared scheme coupling
- When multiple projects use the same scheme, editing that scheme changes behavior for every project using it, which is efficient but risky.
- Project archive
- A reversible action making a project read-only and hidden from most users, preferred over deletion when retention rather than removal is required.
- Team-managed project
- A project type that owns its configuration internally and cannot use shared global schemes, unlike company-managed projects that attach to global schemes.
- Field configuration
- A scheme component controlling whether a field is visible, required, or uses a specific renderer, independent of which screens display the field.
- Screen mapping
- The assignment of screens to operations such as create, edit, view, or transition; a field absent from the relevant screen cannot be edited there.
- Custom field context
- A restriction limiting a custom field to selected projects and issue types, optionally limiting available options; a field without context is global.
- Sub-task issue type
- An issue type flagged as a sub-task that must appear in the parent issue type scheme and workflow before it can be created under a parent.
- Validator
- A workflow transition check that runs after the user attempts the transition and blocks completion when its condition is not satisfied.
- Post function
- An action executed after a transition succeeds, such as setting resolution or firing an event; functions run in order and dependent order matters.
- Global transition
- A transition available from every status in a workflow, commonly used for cross-cutting actions like closing an issue from any state.
- Workflow draft
- An editable copy of a published workflow that does not affect running issues until published, at which point in-flight issues migrate.
- Issue security level
- A per-issue visibility setting from an issue security scheme; users need the matching level and the Set Issue Security permission to see the issue.
- Directory order
- The sequence of configured user directories; the first directory containing a user determines authentication and profile data for that user.
- User deactivation
- A reversible action that frees a license seat while preserving the user's issues and history, unlike deletion which can orphan assignments.
- Permission helper
- A diagnostic tool that explains whether a given user holds a permission by listing each rule that grants or withholds it.
- Automation actor
- The user identity under which an automation rule executes; it must hold permission for each action or the action is skipped or fails.
- JQL condition
- An automation condition evaluated after the trigger that filters matching issues; a failed condition stops the rule and logs condition not met.
- Notification scheme
- A mapping of events to recipient types attached to a project; a project with an empty scheme sends no notifications for any event.
- Scheduled automation rule
- A rule that runs a JQL query on a cron schedule rather than on an issue event, suited to recurring maintenance such as stale issue cleanup.
- CSV import
- A bulk issue creation path mapping columns to fields, requiring project, issue type, and summary, with row-level failures reported after completion.
- XML backup restore
- The supported full-site migration path that replaces the target instance and requires matching versions or a defined upgrade path.
- Integrity checker
- A diagnostic that flags orphaned issues, broken workflow references, and inconsistent scheme mappings, typically run after imports or scheme changes.
- Index versus data integrity
- A corrupt search index yields wrong JQL results while the database stays correct, so reindexing repairs search without changing stored data.
- Issue link type
- A global, directional relationship such as blocks or relates to; creating one link automatically creates the reciprocal link on the other issue.
- Application link
- A trust or OAuth configuration connecting Jira to another Atlassian application, enabling shared user search and remote issue links.
- Outbound webhook
- A push of issue event data as JSON to an external endpoint; it is one-directional and retries on failure according to configuration.
- REST API versioning
- Jira exposes versioned REST paths such as api/2 and api/3, whose payloads differ notably in how rich text fields are represented.