Jira Application Administration, Configuration, and System Settings
Where global settings live
Application administration is about the settings that apply instance-wide before any project exists. A candidate should be fluent in the distinction between global settings (general configuration, look and feel, application links, mail, advanced settings, audit log) and project-scoped settings. Know where each lives in the admin menu and what a change affects. General configuration controls base URL, default language, attachment size, and the maximum number of issues returned by searches; advanced settings expose raw property keys that override defaults.
The audit log records configuration changes with actor and timestamp, and is the first place to look when something changed unexpectedly. Application links connect Jira to other Atlassian or third-party tools and underpin integrations. Mail settings govern outgoing notifications; a misconfigured SMTP host silently breaks all notifications.
Traps to watch
- Confusing a global permission (can this user log in or administer Jira at all?) with a project permission (can this user act inside this project?). Global permissions are granted to groups, not to individuals, and that restriction is a frequent distractor.
- Assuming a setting change is instant everywhere; some caches and indexes need a reindex or refresh.
- Mixing up default values with values already customized by a prior admin.
Rule of thumb
When a question asks "what is the fastest way to confirm who changed this setting," the answer is almost always the audit log, not a permission scheme review. Treat global permissions as the outermost gate: no project role can grant access to a user who fails the global gate.
Worked example: users report they cannot log in at all. Check global permissions for Jira Users first; if the group is missing, no project configuration will help.