ACP-620 cheat sheet

Global permission administration is separate from project permissions: Jira Administrators are granted through the global permission "Jira Administrators", not through a group named jira-administrators by default.

Application access is controlled by application access settings (Jira Core, Jira Software, Jira Service Management); a user with no application access can authenticate but cannot use the product.

The default dashboard, default issue navigator columns, and default user time zone are set in General Configuration and apply to users who have not personalized them.

Option schemes (status, priority, resolution, severity) are global; changing an option name updates it everywhere, while deleting an option requires a replacement mapping for existing issues.

The audit log records configuration changes with actor, time, and before/after values; it is the primary evidence source for post-incident configuration review.

Mail queue and outgoing mail settings live under System > Outgoing Mail; the mail queue can be flushed or cleared, and a stuck queue usually indicates SMTP connectivity or authentication failure.

Jira Data Center adds node-level concerns: shared home directory, cluster locks, and index replication; a node out of sync shows stale or missing search results until reindexed.

Reindexing is required after changes to custom field searchers, field configurations used by JQL, or issue type schemes; a background reindex is preferred to avoid downtime.

Licensing is per application and per user tier; users count against the highest application tier they can access, and inactive users still consume a license unless deactivated.

A project is defined by four schemes: issue type scheme, workflow scheme, field configuration scheme, and issue type screen scheme; permission, notification, and issue security schemes attach separately.

Scheme sharing is the key design decision: shared schemes reduce maintenance but couple projects, so a change for one project affects every project sharing the scheme.

Moving a project between schemes requires a migration step that maps issue types and statuses; unmapped statuses cause issues to become unreadable in the new workflow.

Project roles are the recommended abstraction for permissions and notifications; roles are per-project and can be populated by groups, single users, or directory groups.

The project category groups projects for the browse-project directory and can drive shared permission or notification schemes via category-based role membership.

Archiving a project makes it read-only and hidden from most users; it is reversible and preferred over deletion for retention.

Deleting a project is permanent and removes issues, attachments, and its unique schemes; shared schemes survive deletion.

Project keys are immutable after creation in modern Jira Cloud and effectively fixed in Data Center; renaming a key requires a project move or XML export/import.

Simplified vs. company-managed projects differ in where schemes live: team-managed projects own their configuration and cannot use shared global schemes.

Field configuration controls whether a field is visible, required, or rendered with a specific renderer; it does not control which screen shows the field.

Screens control field visibility per operation (create, edit, view, transition); a field on no screen for an operation cannot be edited in that operation.

Field configuration scheme maps issue types to field configurations; issue type scheme maps issue types to projects; both must align for a field to behave as intended.

Required fields set in field configuration are enforced on create and edit; required fields set on a workflow transition screen are enforced only for that transition.

Custom field context limits a field to selected projects and issue types and can restrict options; a field with no context is global.

Changing a custom field's searcher requires a reindex before JQL reflects the new behavior; changing only the name does not.

Issue type schemes can be shared; adding an issue type to a shared scheme adds it to every project using the scheme, which may require workflow mapping.

Sub-tasks are issue types flagged as sub-task; they must be included in the parent's issue type scheme and workflow to be creatable.

Field configuration does not hide a field from JQL; searchability depends on the field's searcher, not its visibility.

A workflow is a directed graph of statuses and transitions; a status with no outgoing transition is terminal for that workflow and blocks further progress.

Conditions gate whether a transition is offered; validators block the transition after it is attempted; post functions run after the transition succeeds.

Conditions are evaluated for display; if a condition fails, the transition button is hidden rather than shown and rejected.

The "Allow only users with permission" condition is preferred over group checks for permission-aligned gating because it follows the permission scheme.

Post functions execute in order; common ones set the resolution, assign the issue, fire an event, or update a field, and order matters when functions depend on each other.

The workflow scheme maps issue types to workflows; a project can have multiple workflows, and the default workflow handles issue types with no explicit mapping.

Global transitions apply to all statuses in a workflow and are useful for cross-cutting actions such as closing from any state.

Workflow drafts allow editing a published workflow without immediate effect; publishing migrates in-flight issues to the new definition.

The workflow designer and the text editor are equivalent views; complex logic such as conditional validators is easier to audit in text mode.

Permission schemes grant permissions to project roles, groups, single users, or the reporter/assignee/current-user; roles are resolved per project at evaluation time.

Global permissions (e.g., Browse Users, Create Shared Objects, Jira Administrators) are separate from project permissions and are not inherited from project roles.

Issue-level security uses an issue security scheme with levels; a user must have the Set Issue Security permission and a matching level to see the issue.

Group membership changes take effect immediately for permission evaluation but may require re-login for cached application access in some deployments.

Directory order matters: when multiple user directories are configured, the first directory that contains a user wins for authentication and profile data.

Deactivating a user frees a license seat but preserves their issues and history; deleting a user can orphan assignments unless reassigned first.

Permission helper tools report why a user does or does not have a permission by listing each granting or denying rule.

Anonymous access is a global permission plus project permission combination; both must allow it for unauthenticated browsing.

Automation rules consist of a trigger, optional conditions, and actions; the trigger determines whether the rule runs on issue events, schedules, or incoming webhooks.

JQL conditions filter issues after the trigger; a rule that fires but fails its condition performs no actions and logs a condition-not-met entry.

Automation runs as an actor: the rule actor must have permission to perform each action, or the action is skipped or fails.

Notification schemes map events to recipients; events are fired by workflow post functions or by system events such as issue created or commented.

The default notification scheme applies to projects with no explicit scheme; a project with an empty notification scheme sends no notifications.

Automation audit logs record rule runs, including which issues matched and which actions succeeded or failed; they are the first place to diagnose a misbehaving rule.

Smart values reference issue fields and can be transformed with functions; an unresolved smart value renders empty rather than raising an error.

Scheduled rules run as a JQL query on a cron schedule; they are suited to recurring maintenance such as stale-issue cleanup.

Webhook triggers accept a JSON payload and can create or update issues; the payload must be mapped to fields explicitly.

CSV import maps columns to fields and requires a project, issue type, and summary; unmapped required fields cause row-level failures reported after import.

The external system importer supports users, groups, and issues with configurable mappings and runs in stages with a dry-run validation step.

XML backup and restore is the supported path for full-site migration; the restore replaces the target instance and requires matching application versions or an upgrade path.

Project import brings issues, versions, components, and attachments from another Jira instance but does not import global schemes unless configured.

Integrity checker flags orphaned issues, broken workflow references, and inconsistent scheme mappings; run it after bulk imports or scheme changes.

Bulk change operations respect permissions and workflow validators; a transition blocked by a validator will fail for the whole bulk operation.

Attachment storage location and size limits are configured globally; exceeding the limit blocks uploads without affecting existing attachments.

Index integrity is separate from data integrity: a corrupt index produces wrong search results while the database remains correct, so reindexing is the remedy.

Issue linking uses link types (e.g., blocks, is blocked by, relates to) that are global and directional; both directions are created automatically.

An application link enables OAuth or trust-based communication between Jira and another Atlassian application, powering shared user search and remote issue links.

Remote issue links connect Jira issues to external systems via URL and relationship metadata; they do not create issues in the remote system.

Webhooks push issue events to external endpoints as JSON; they are outbound only and retry on failure according to configuration.

The REST API is versioned by path (e.g., /rest/api/2 or /rest/api/3); field payloads differ between versions, particularly for rich text.

Marketplace apps extend Jira through the plugin framework; app compatibility must be verified against the Jira version before upgrade.

The Jira Software and Jira Service Management applications layer features on Jira Core; a user needs access to the relevant application to see boards or queues.

Single sign-on integration via SAML or OIDC delegates authentication to an identity provider; Jira still resolves authorization through its own directories and permissions.

Global permission administration is separate from project permissions: Jira Administrators are granted through the global permission "Jira Administrators", not through a group named jira-administrators by default.

Application access is controlled by application access settings (Jira Core, Jira Software, Jira Service Management); a user with no application access can authenticate but cannot use the product.

The default dashboard, default issue navigator columns, and default user time zone are set in General Configuration and apply to users who have not personalized them.

Option schemes (status, priority, resolution, severity) are global; changing an option name updates it everywhere, while deleting an option requires a replacement mapping for existing issues.

The audit log records configuration changes with actor, time, and before/after values; it is the primary evidence source for post-incident configuration review.

Mail queue and outgoing mail settings live under System > Outgoing Mail; the mail queue can be flushed or cleared, and a stuck queue usually indicates SMTP connectivity or authentication failure.

Jira Data Center adds node-level concerns: shared home directory, cluster locks, and index replication; a node out of sync shows stale or missing search results until reindexed.

Reindexing is required after changes to custom field searchers, field configurations used by JQL, or issue type schemes; a background reindex is preferred to avoid downtime.

Licensing is per application and per user tier; users count against the highest application tier they can access, and inactive users still consume a license unless deactivated.

A project is defined by four schemes: issue type scheme, workflow scheme, field configuration scheme, and issue type screen scheme; permission, notification, and issue security schemes attach separately.

Scheme sharing is the key design decision: shared schemes reduce maintenance but couple projects, so a change for one project affects every project sharing the scheme.

Moving a project between schemes requires a migration step that maps issue types and statuses; unmapped statuses cause issues to become unreadable in the new workflow.

Project roles are the recommended abstraction for permissions and notifications; roles are per-project and can be populated by groups, single users, or directory groups.

The project category groups projects for the browse-project directory and can drive shared permission or notification schemes via category-based role membership.

Archiving a project makes it read-only and hidden from most users; it is reversible and preferred over deletion for retention.

Deleting a project is permanent and removes issues, attachments, and its unique schemes; shared schemes survive deletion.

Project keys are immutable after creation in modern Jira Cloud and effectively fixed in Data Center; renaming a key requires a project move or XML export/import.

Simplified vs. company-managed projects differ in where schemes live: team-managed projects own their configuration and cannot use shared global schemes.

Field configuration controls whether a field is visible, required, or rendered with a specific renderer; it does not control which screen shows the field.

Screens control field visibility per operation (create, edit, view, transition); a field on no screen for an operation cannot be edited in that operation.

Field configuration scheme maps issue types to field configurations; issue type scheme maps issue types to projects; both must align for a field to behave as intended.

Required fields set in field configuration are enforced on create and edit; required fields set on a workflow transition screen are enforced only for that transition.

Custom field context limits a field to selected projects and issue types and can restrict options; a field with no context is global.

Changing a custom field's searcher requires a reindex before JQL reflects the new behavior; changing only the name does not.

Issue type schemes can be shared; adding an issue type to a shared scheme adds it to every project using the scheme, which may require workflow mapping.

Sub-tasks are issue types flagged as sub-task; they must be included in the parent's issue type scheme and workflow to be creatable.

Field configuration does not hide a field from JQL; searchability depends on the field's searcher, not its visibility.

A workflow is a directed graph of statuses and transitions; a status with no outgoing transition is terminal for that workflow and blocks further progress.

Conditions gate whether a transition is offered; validators block the transition after it is attempted; post functions run after the transition succeeds.

Conditions are evaluated for display; if a condition fails, the transition button is hidden rather than shown and rejected.

The "Allow only users with permission" condition is preferred over group checks for permission-aligned gating because it follows the permission scheme.

Post functions execute in order; common ones set the resolution, assign the issue, fire an event, or update a field, and order matters when functions depend on each other.

The workflow scheme maps issue types to workflows; a project can have multiple workflows, and the default workflow handles issue types with no explicit mapping.

Global transitions apply to all statuses in a workflow and are useful for cross-cutting actions such as closing from any state.

Workflow drafts allow editing a published workflow without immediate effect; publishing migrates in-flight issues to the new definition.

The workflow designer and the text editor are equivalent views; complex logic such as conditional validators is easier to audit in text mode.

Permission schemes grant permissions to project roles, groups, single users, or the reporter/assignee/current-user; roles are resolved per project at evaluation time.

Global permissions (e.g., Browse Users, Create Shared Objects, Jira Administrators) are separate from project permissions and are not inherited from project roles.

Issue-level security uses an issue security scheme with levels; a user must have the Set Issue Security permission and a matching level to see the issue.

Group membership changes take effect immediately for permission evaluation but may require re-login for cached application access in some deployments.

Directory order matters: when multiple user directories are configured, the first directory that contains a user wins for authentication and profile data.

Deactivating a user frees a license seat but preserves their issues and history; deleting a user can orphan assignments unless reassigned first.

Permission helper tools report why a user does or does not have a permission by listing each granting or denying rule.

Anonymous access is a global permission plus project permission combination; both must allow it for unauthenticated browsing.

Automation rules consist of a trigger, optional conditions, and actions; the trigger determines whether the rule runs on issue events, schedules, or incoming webhooks.

JQL conditions filter issues after the trigger; a rule that fires but fails its condition performs no actions and logs a condition-not-met entry.

Automation runs as an actor: the rule actor must have permission to perform each action, or the action is skipped or fails.

Notification schemes map events to recipients; events are fired by workflow post functions or by system events such as issue created or commented.

The default notification scheme applies to projects with no explicit scheme; a project with an empty notification scheme sends no notifications.

Automation audit logs record rule runs, including which issues matched and which actions succeeded or failed; they are the first place to diagnose a misbehaving rule.

Smart values reference issue fields and can be transformed with functions; an unresolved smart value renders empty rather than raising an error.

Scheduled rules run as a JQL query on a cron schedule; they are suited to recurring maintenance such as stale-issue cleanup.

Webhook triggers accept a JSON payload and can create or update issues; the payload must be mapped to fields explicitly.

CSV import maps columns to fields and requires a project, issue type, and summary; unmapped required fields cause row-level failures reported after import.

The external system importer supports users, groups, and issues with configurable mappings and runs in stages with a dry-run validation step.

XML backup and restore is the supported path for full-site migration; the restore replaces the target instance and requires matching application versions or an upgrade path.

Project import brings issues, versions, components, and attachments from another Jira instance but does not import global schemes unless configured.

Integrity checker flags orphaned issues, broken workflow references, and inconsistent scheme mappings; run it after bulk imports or scheme changes.

Bulk change operations respect permissions and workflow validators; a transition blocked by a validator will fail for the whole bulk operation.

Attachment storage location and size limits are configured globally; exceeding the limit blocks uploads without affecting existing attachments.

Index integrity is separate from data integrity: a corrupt index produces wrong search results while the database remains correct, so reindexing is the remedy.

Issue linking uses link types (e.g., blocks, is blocked by, relates to) that are global and directional; both directions are created automatically.

An application link enables OAuth or trust-based communication between Jira and another Atlassian application, powering shared user search and remote issue links.

Remote issue links connect Jira issues to external systems via URL and relationship metadata; they do not create issues in the remote system.

Webhooks push issue events to external endpoints as JSON; they are outbound only and retry on failure according to configuration.

The REST API is versioned by path (e.g., /rest/api/2 or /rest/api/3); field payloads differ between versions, particularly for rich text.

Marketplace apps extend Jira through the plugin framework; app compatibility must be verified against the Jira version before upgrade.

The Jira Software and Jira Service Management applications layer features on Jira Core; a user needs access to the relevant application to see boards or queues.

Single sign-on integration via SAML or OIDC delegates authentication to an identity provider; Jira still resolves authorization through its own directories and permissions.

Global permission administration is separate from project permissions: Jira Administrators are granted through the global permission "Jira Administrators", not through a group named jira-administrators by default.

Application access is controlled by application access settings (Jira Core, Jira Software, Jira Service Management); a user with no application access can authenticate but cannot use the product.

The default dashboard, default issue navigator columns, and default user time zone are set in General Configuration and apply to users who have not personalized them.

Option schemes (status, priority, resolution, severity) are global; changing an option name updates it everywhere, while deleting an option requires a replacement mapping for existing issues.

The audit log records configuration changes with actor, time, and before/after values; it is the primary evidence source for post-incident configuration review.

Mail queue and outgoing mail settings live under System > Outgoing Mail; the mail queue can be flushed or cleared, and a stuck queue usually indicates SMTP connectivity or authentication failure.

Jira Data Center adds node-level concerns: shared home directory, cluster locks, and index replication; a node out of sync shows stale or missing search results until reindexed.

Reindexing is required after changes to custom field searchers, field configurations used by JQL, or issue type schemes; a background reindex is preferred to avoid downtime.

Licensing is per application and per user tier; users count against the highest application tier they can access, and inactive users still consume a license unless deactivated.

A project is defined by four schemes: issue type scheme, workflow scheme, field configuration scheme, and issue type screen scheme; permission, notification, and issue security schemes attach separately.

Scheme sharing is the key design decision: shared schemes reduce maintenance but couple projects, so a change for one project affects every project sharing the scheme.

Moving a project between schemes requires a migration step that maps issue types and statuses; unmapped statuses cause issues to become unreadable in the new workflow.

Project roles are the recommended abstraction for permissions and notifications; roles are per-project and can be populated by groups, single users, or directory groups.

The project category groups projects for the browse-project directory and can drive shared permission or notification schemes via category-based role membership.

Archiving a project makes it read-only and hidden from most users; it is reversible and preferred over deletion for retention.

Deleting a project is permanent and removes issues, attachments, and its unique schemes; shared schemes survive deletion.

Project keys are immutable after creation in modern Jira Cloud and effectively fixed in Data Center; renaming a key requires a project move or XML export/import.

Simplified vs. company-managed projects differ in where schemes live: team-managed projects own their configuration and cannot use shared global schemes.

Field configuration controls whether a field is visible, required, or rendered with a specific renderer; it does not control which screen shows the field.

Screens control field visibility per operation (create, edit, view, transition); a field on no screen for an operation cannot be edited in that operation.

Field configuration scheme maps issue types to field configurations; issue type scheme maps issue types to projects; both must align for a field to behave as intended.

Required fields set in field configuration are enforced on create and edit; required fields set on a workflow transition screen are enforced only for that transition.

Custom field context limits a field to selected projects and issue types and can restrict options; a field with no context is global.

Changing a custom field's searcher requires a reindex before JQL reflects the new behavior; changing only the name does not.

Issue type schemes can be shared; adding an issue type to a shared scheme adds it to every project using the scheme, which may require workflow mapping.

Sub-tasks are issue types flagged as sub-task; they must be included in the parent's issue type scheme and workflow to be creatable.

Field configuration does not hide a field from JQL; searchability depends on the field's searcher, not its visibility.

A workflow is a directed graph of statuses and transitions; a status with no outgoing transition is terminal for that workflow and blocks further progress.

Conditions gate whether a transition is offered; validators block the transition after it is attempted; post functions run after the transition succeeds.

Conditions are evaluated for display; if a condition fails, the transition button is hidden rather than shown and rejected.

The "Allow only users with permission" condition is preferred over group checks for permission-aligned gating because it follows the permission scheme.

Post functions execute in order; common ones set the resolution, assign the issue, fire an event, or update a field, and order matters when functions depend on each other.

The workflow scheme maps issue types to workflows; a project can have multiple workflows, and the default workflow handles issue types with no explicit mapping.

Global transitions apply to all statuses in a workflow and are useful for cross-cutting actions such as closing from any state.

Workflow drafts allow editing a published workflow without immediate effect; publishing migrates in-flight issues to the new definition.

The workflow designer and the text editor are equivalent views; complex logic such as conditional validators is easier to audit in text mode.

Permission schemes grant permissions to project roles, groups, single users, or the reporter/assignee/current-user; roles are resolved per project at evaluation time.

Global permissions (e.g., Browse Users, Create Shared Objects, Jira Administrators) are separate from project permissions and are not inherited from project roles.

Issue-level security uses an issue security scheme with levels; a user must have the Set Issue Security permission and a matching level to see the issue.

Group membership changes take effect immediately for permission evaluation but may require re-login for cached application access in some deployments.

Directory order matters: when multiple user directories are configured, the first directory that contains a user wins for authentication and profile data.

Deactivating a user frees a license seat but preserves their issues and history; deleting a user can orphan assignments unless reassigned first.

Permission helper tools report why a user does or does not have a permission by listing each granting or denying rule.

Anonymous access is a global permission plus project permission combination; both must allow it for unauthenticated browsing.

Automation rules consist of a trigger, optional conditions, and actions; the trigger determines whether the rule runs on issue events, schedules, or incoming webhooks.

JQL conditions filter issues after the trigger; a rule that fires but fails its condition performs no actions and logs a condition-not-met entry.

Automation runs as an actor: the rule actor must have permission to perform each action, or the action is skipped or fails.

Notification schemes map events to recipients; events are fired by workflow post functions or by system events such as issue created or commented.

The default notification scheme applies to projects with no explicit scheme; a project with an empty notification scheme sends no notifications.

Automation audit logs record rule runs, including which issues matched and which actions succeeded or failed; they are the first place to diagnose a misbehaving rule.

Smart values reference issue fields and can be transformed with functions; an unresolved smart value renders empty rather than raising an error.

Scheduled rules run as a JQL query on a cron schedule; they are suited to recurring maintenance such as stale-issue cleanup.

Webhook triggers accept a JSON payload and can create or update issues; the payload must be mapped to fields explicitly.

CSV import maps columns to fields and requires a project, issue type, and summary; unmapped required fields cause row-level failures reported after import.

The external system importer supports users, groups, and issues with configurable mappings and runs in stages with a dry-run validation step.

XML backup and restore is the supported path for full-site migration; the restore replaces the target instance and requires matching application versions or an upgrade path.

Project import brings issues, versions, components, and attachments from another Jira instance but does not import global schemes unless configured.

Integrity checker flags orphaned issues, broken workflow references, and inconsistent scheme mappings; run it after bulk imports or scheme changes.

Bulk change operations respect permissions and workflow validators; a transition blocked by a validator will fail for the whole bulk operation.

Attachment storage location and size limits are configured globally; exceeding the limit blocks uploads without affecting existing attachments.

Index integrity is separate from data integrity: a corrupt index produces wrong search results while the database remains correct, so reindexing is the remedy.

Issue linking uses link types (e.g., blocks, is blocked by, relates to) that are global and directional; both directions are created automatically.

An application link enables OAuth or trust-based communication between Jira and another Atlassian application, powering shared user search and remote issue links.

Remote issue links connect Jira issues to external systems via URL and relationship metadata; they do not create issues in the remote system.

Webhooks push issue events to external endpoints as JSON; they are outbound only and retry on failure according to configuration.

The REST API is versioned by path (e.g., /rest/api/2 or /rest/api/3); field payloads differ between versions, particularly for rich text.

Marketplace apps extend Jira through the plugin framework; app compatibility must be verified against the Jira version before upgrade.

The Jira Software and Jira Service Management applications layer features on Jira Core; a user needs access to the relevant application to see boards or queues.

Single sign-on integration via SAML or OIDC delegates authentication to an identity provider; Jira still resolves authorization through its own directories and permissions.

Global permission administration is separate from project permissions: Jira Administrators are granted through the global permission "Jira Administrators", not through a group named jira-administrators by default.

Application access is controlled by application access settings (Jira Core, Jira Software, Jira Service Management); a user with no application access can authenticate but cannot use the product.

The default dashboard, default issue navigator columns, and default user time zone are set in General Configuration and apply to users who have not personalized them.

Option schemes (status, priority, resolution, severity) are global; changing an option name updates it everywhere, while deleting an option requires a replacement mapping for existing issues.

The audit log records configuration changes with actor, time, and before/after values; it is the primary evidence source for post-incident configuration review.

Mail queue and outgoing mail settings live under System > Outgoing Mail; the mail queue can be flushed or cleared, and a stuck queue usually indicates SMTP connectivity or authentication failure.

Jira Data Center adds node-level concerns: shared home directory, cluster locks, and index replication; a node out of sync shows stale or missing search results until reindexed.

Reindexing is required after changes to custom field searchers, field configurations used by JQL, or issue type schemes; a background reindex is preferred to avoid downtime.

Licensing is per application and per user tier; users count against the highest application tier they can access, and inactive users still consume a license unless deactivated.

A project is defined by four schemes: issue type scheme, workflow scheme, field configuration scheme, and issue type screen scheme; permission, notification, and issue security schemes attach separately.

Scheme sharing is the key design decision: shared schemes reduce maintenance but couple projects, so a change for one project affects every project sharing the scheme.

Moving a project between schemes requires a migration step that maps issue types and statuses; unmapped statuses cause issues to become unreadable in the new workflow.

Project roles are the recommended abstraction for permissions and notifications; roles are per-project and can be populated by groups, single users, or directory groups.

The project category groups projects for the browse-project directory and can drive shared permission or notification schemes via category-based role membership.

Archiving a project makes it read-only and hidden from most users; it is reversible and preferred over deletion for retention.

Deleting a project is permanent and removes issues, attachments, and its unique schemes; shared schemes survive deletion.

Project keys are immutable after creation in modern Jira Cloud and effectively fixed in Data Center; renaming a key requires a project move or XML export/import.

Simplified vs. company-managed projects differ in where schemes live: team-managed projects own their configuration and cannot use shared global schemes.

Field configuration controls whether a field is visible, required, or rendered with a specific renderer; it does not control which screen shows the field.

Screens control field visibility per operation (create, edit, view, transition); a field on no screen for an operation cannot be edited in that operation.

Field configuration scheme maps issue types to field configurations; issue type scheme maps issue types to projects; both must align for a field to behave as intended.

Required fields set in field configuration are enforced on create and edit; required fields set on a workflow transition screen are enforced only for that transition.

Custom field context limits a field to selected projects and issue types and can restrict options; a field with no context is global.

Changing a custom field's searcher requires a reindex before JQL reflects the new behavior; changing only the name does not.

Issue type schemes can be shared; adding an issue type to a shared scheme adds it to every project using the scheme, which may require workflow mapping.

Sub-tasks are issue types flagged as sub-task; they must be included in the parent's issue type scheme and workflow to be creatable.

Field configuration does not hide a field from JQL; searchability depends on the field's searcher, not its visibility.

A workflow is a directed graph of statuses and transitions; a status with no outgoing transition is terminal for that workflow and blocks further progress.

Conditions gate whether a transition is offered; validators block the transition after it is attempted; post functions run after the transition succeeds.

Conditions are evaluated for display; if a condition fails, the transition button is hidden rather than shown and rejected.

The "Allow only users with permission" condition is preferred over group checks for permission-aligned gating because it follows the permission scheme.

Post functions execute in order; common ones set the resolution, assign the issue, fire an event, or update a field, and order matters when functions depend on each other.

The workflow scheme maps issue types to workflows; a project can have multiple workflows, and the default workflow handles issue types with no explicit mapping.

Global transitions apply to all statuses in a workflow and are useful for cross-cutting actions such as closing from any state.

Workflow drafts allow editing a published workflow without immediate effect; publishing migrates in-flight issues to the new definition.

The workflow designer and the text editor are equivalent views; complex logic such as conditional validators is easier to audit in text mode.

Permission schemes grant permissions to project roles, groups, single users, or the reporter/assignee/current-user; roles are resolved per project at evaluation time.

Global permissions (e.g., Browse Users, Create Shared Objects, Jira Administrators) are separate from project permissions and are not inherited from project roles.

Issue-level security uses an issue security scheme with levels; a user must have the Set Issue Security permission and a matching level to see the issue.

Group membership changes take effect immediately for permission evaluation but may require re-login for cached application access in some deployments.

Directory order matters: when multiple user directories are configured, the first directory that contains a user wins for authentication and profile data.

Deactivating a user frees a license seat but preserves their issues and history; deleting a user can orphan assignments unless reassigned first.

Permission helper tools report why a user does or does not have a permission by listing each granting or denying rule.

Anonymous access is a global permission plus project permission combination; both must allow it for unauthenticated browsing.

Automation rules consist of a trigger, optional conditions, and actions; the trigger determines whether the rule runs on issue events, schedules, or incoming webhooks.

JQL conditions filter issues after the trigger; a rule that fires but fails its condition performs no actions and logs a condition-not-met entry.

Automation runs as an actor: the rule actor must have permission to perform each action, or the action is skipped or fails.

Notification schemes map events to recipients; events are fired by workflow post functions or by system events such as issue created or commented.

The default notification scheme applies to projects with no explicit scheme; a project with an empty notification scheme sends no notifications.

Automation audit logs record rule runs, including which issues matched and which actions succeeded or failed; they are the first place to diagnose a misbehaving rule.

Smart values reference issue fields and can be transformed with functions; an unresolved smart value renders empty rather than raising an error.

Scheduled rules run as a JQL query on a cron schedule; they are suited to recurring maintenance such as stale-issue cleanup.

Webhook triggers accept a JSON payload and can create or update issues; the payload must be mapped to fields explicitly.

CSV import maps columns to fields and requires a project, issue type, and summary; unmapped required fields cause row-level failures reported after import.

The external system importer supports users, groups, and issues with configurable mappings and runs in stages with a dry-run validation step.

XML backup and restore is the supported path for full-site migration; the restore replaces the target instance and requires matching application versions or an upgrade path.

Project import brings issues, versions, components, and attachments from another Jira instance but does not import global schemes unless configured.

Integrity checker flags orphaned issues, broken workflow references, and inconsistent scheme mappings; run it after bulk imports or scheme changes.

Bulk change operations respect permissions and workflow validators; a transition blocked by a validator will fail for the whole bulk operation.

Attachment storage location and size limits are configured globally; exceeding the limit blocks uploads without affecting existing attachments.

Index integrity is separate from data integrity: a corrupt index produces wrong search results while the database remains correct, so reindexing is the remedy.

Issue linking uses link types (e.g., blocks, is blocked by, relates to) that are global and directional; both directions are created automatically.

An application link enables OAuth or trust-based communication between Jira and another Atlassian application, powering shared user search and remote issue links.

Remote issue links connect Jira issues to external systems via URL and relationship metadata; they do not create issues in the remote system.

Webhooks push issue events to external endpoints as JSON; they are outbound only and retry on failure according to configuration.

The REST API is versioned by path (e.g., /rest/api/2 or /rest/api/3); field payloads differ between versions, particularly for rich text.

Marketplace apps extend Jira through the plugin framework; app compatibility must be verified against the Jira version before upgrade.

The Jira Software and Jira Service Management applications layer features on Jira Core; a user needs access to the relevant application to see boards or queues.

Single sign-on integration via SAML or OIDC delegates authentication to an identity provider; Jira still resolves authorization through its own directories and permissions.