Jira Not Working? Common Errors & Fixes

Jira gets slow when boards and searches load too many issues, when marketplace apps or heavy automation add load, or when the browser has extensions and stale cache. Check Atlassian's status page, test in incognito, then trim board filters and remove heavy apps.

A blank Jira page or endlessly spinning board is usually caused by a browser extension, stale cache/cookies or an Atlassian incident. Test in a private window with extensions off and hard-refresh.

If someone doesn't get Jira emails, check their personal notification settings, the project's notification scheme, the event fired by the workflow transition, and their permissions. Suppressed addresses need Atlassian Support.

Issues missing from a Jira board or backlog are almost always hidden by the board's saved filter, a Kanban sub-filter, an active quick filter, or statuses that aren't mapped to columns.

A Jira automation rule that never runs is usually disabled, scoped to the wrong project, waiting for an event that never fires, or throttled by the plan's monthly automation limit. The audit log tells you which.

Jira Cloud meters automation in steps per month; when the allowance runs out, rules are throttled until the next cycle. Cut noisy rules or upgrade.

When the Jira login page just refreshes or loops, the browser usually can't set Atlassian's cookies. Allow cookies, clear cache, try incognito, and check status.atlassian.com.

This JQL error means Jira can't resolve the field name or the field isn't searchable. Use the JQL name (e.g. affectedVersion), give the custom field a search template, or check Browse permission.

Start sprint is greyed out when you lack sprint permission, another sprint is already active, the sprint is empty, or you're not on a Scrum board.

Attachment uploads fail when the session token is stale, the user lacks Create Attachments permission, or attachments are disabled site-wide. Reload the page and check permissions.