Jira Not Working? 15 Common Jira Errors and How to Fix Them in 2026

Why Jira Errors Are So Frustrating (And So Fixable)

Jira’s architecture — with its layers of projects, schemes, permissions, workflows, and integrations — creates many opportunities for misconfigurations. Most errors that teams encounter aren’t bugs; they’re configuration issues that have a specific fix. The challenge is knowing where to look. This guide organizes the 15 most common issues by category so you can find your fix quickly.

Authentication & Access Errors

Error 1: Jira Login Loop (Keeps Redirecting to Login Page)

What happens: You enter your credentials, get redirected to a loading screen, then back to the login page — repeatedly, never reaching your Jira dashboard.

Cause: Almost always a cookie or session storage issue, or a conflict between your browser’s stored session and Jira’s current session state.

Fix: Open your browser’s developer tools (F12), go to Application → Storage → Cookies, find the cookies for your Atlassian domain, and delete them all. Then clear your browser cache (Ctrl+Shift+Delete). Try logging in again. If this doesn’t work, try a private/incognito window. If that works, the issue is in your browser profile’s stored data.

Error 2: SSO / SAML Authentication Failure

What happens: You’re redirected to your company’s identity provider (Okta, Azure AD, Google), successfully authenticate there, but get bounced back to Jira with a SAML error or “Authentication failed” message.

Cause: Mismatch between the SAML assertion’s NameID format and what Jira expects, expired SAML certificate, or a clock skew between the identity provider and Jira’s servers.

Fix: Your Jira admin should check the SAML configuration under Administration → User Management → SAML Single Sign-On. Verify that the NameID format matches your identity provider’s settings. Check certificate expiry. For clock skew issues, ensure both servers are synchronized via NTP. In Atlassian Cloud, you can view SAML error details in the Atlassian admin console under Security → SAML authentication.

Error 3: “You don’t have permission” on a Project You Can See

What happens: A user can see a project in the project list but gets a permission denied error when trying to create issues, transition tasks, or access certain issue types.

Cause: Jira’s permission scheme controls what each user can DO, separate from whether they can see the project. The user may be in a group with View permission but not Edit/Create permission.

Fix: Go to Project Settings → Permissions for the affected project. Review the “Create Issues”, “Edit Issues”, and “Transition Issues” permission entries. Check which groups or roles are included. Add the user to the appropriate group (e.g., “Software Team Member” or “Developers”) or update the permission scheme to include their role. If you’re using project roles, assign the user to the correct role in Project Settings → People.

Board & Issue Display Errors

Error 4: Jira Board Shows Blank / No Issues

What happens: Your Scrum or Kanban board is empty even though you know issues exist in the project. The backlog may also be empty, or issues exist in the backlog but won’t move to the board.

Cause: Board filter is restricting which issues appear, or issues aren’t in the correct sprint/status that the board is configured to show.

Fix: Click Board Settings → General and review the Saved Filter. Click “Edit Filter Query” and check the JQL. Look for overly restrictive conditions like project = “ABC” AND sprint in openSprints() AND assignee = currentUser(). If the filter is too narrow, issues won’t appear for all users. Widen the filter by removing the assignee restriction. Also check that your issues are in the correct column/status that the board’s Column Configuration maps to.

Error 5: Issues Missing from Sprint / Appearing in Wrong Sprint

What happens: Issues you added to the active sprint aren’t showing up on the board, or they’re showing in the wrong sprint.

Cause: Usually a sprint field value mismatch or an issue that was added to a sprint while the sprint filter was active but the sprint field wasn’t actually saved.

Fix: Open one of the missing issues directly and check the Sprint field. If it shows the correct sprint, the board filter is the problem (see Error 4 above). If the Sprint field is empty, manually set it to the current sprint. For bulk fixing: go to the Backlog view → select affected issues → right-click → Move to Sprint.

Error 6: Jira Board Columns Not Matching Workflow

What happens: Issues can’t be dragged to certain columns, or dragging them doesn’t change the actual workflow status.

Cause: Board column configuration and the project’s workflow are out of sync. Every board column must be mapped to one or more workflow statuses.

Fix: Go to Board Settings → Columns. Each column should have at least one workflow status mapped to it (shown as colored pills under each column name). If a status exists in your workflow but isn’t shown in any column, drag it from the “Unmapped Statuses” section to the appropriate column. After saving, issues with those statuses will appear in the correct column and can be dragged properly.

Automation Errors

Error 7: Jira Automation Rule Shows “SOME ERRORS” Status

What happens: Your automation rule runs, the audit log shows “SOME ERRORS” in yellow, and the rule either partially completes or fails silently for some issues.

Cause: “SOME ERRORS” means the rule succeeded for some executions but failed for others. Common causes: the rule tries to update a field that doesn’t exist on certain issue types, transition an issue using a workflow transition that doesn’t exist for that status, or assign to a user who doesn’t have project access.

Fix: Click the “SOME ERRORS” status to open the execution details. Look at the failed executions and read the specific error message for each. Common fixes: add an “Issue Type” condition to limit the rule to types that have the relevant field, use the correct transition name from the workflow configuration, and verify that the assignee being set is a member of the project.

Error 8: Automation Rule Not Triggering at All

What happens: You set up an automation rule, perform the trigger action, but nothing happens. The audit log shows no recent executions.

Cause: The rule may be disabled, the trigger conditions aren’t being met, or there’s a scope issue (rule is set to a project but you’re triggering it in a different project).

Fix: First confirm the rule is enabled (blue toggle in the rule list). Check the rule’s trigger conditions carefully — JQL filters in the trigger often require exact field values. Verify the project scope: in Jira Cloud, global rules and project rules are managed separately. Try manually clicking “Run” on the rule for a specific issue to test it. This shows you exactly why it succeeded or failed.

Error 9: Smart Values Returning Empty or Wrong Data

What happens: Your automation uses {{issue.summary}} or {{issue.assignee.displayName}} in a notification or comment, but the output is blank or shows the raw {{variable}} text.

Cause: Syntax error in the smart value, the field is null/empty for that issue, or the wrong context is being referenced (e.g., using issue fields when the trigger is a comment event, requiring {{comment.body}} instead).

Fix: Check the Atlassian smart values reference documentation for the exact syntax. Key pitfall: field names are case-sensitive ({{issue.summary}} works, {{issue.Summary}} does not). For custom fields, use the format {{issue.customfield_XXXXX}} where XXXXX is the field ID. Find the field ID in Jira’s field configuration. Test with the “Audit Log” by running the rule manually and reading the execution details to see what the smart value resolved to.

Performance Issues

Error 10: Jira Running Extremely Slow

What happens: Pages take 10+ seconds to load, filters run slowly, and the board takes forever to open. This degrades over time or spikes at certain times of day.

Cause: For Jira Cloud, this is usually a temporary service degradation — check status.atlassian.com. For Server/Data Center, common causes include: unoptimized JQL filters without indexes, too many live dashboards with complex gadgets, or insufficient memory allocation.

Fix (Cloud): Check status.atlassian.com for active incidents. If none, try clearing your browser cache. Complex Jira filters with CONTAINS (~ operator) are inherently slow — rewrite filters using equality operators (= and IN) where possible. For Data Center: increase JVM heap memory, identify slow queries using the Jira support zip, and check for plugins consuming excessive resources in Administration → Logging and Profiling → Profiling.

Error 11: Jira Search (Issue Navigator) Not Returning Expected Results

What happens: You search for an issue you know exists, but it doesn’t appear in results. Or your JQL filter returns different results than expected.

Cause: Usually a JQL syntax issue, a stale Lucene search index (for Server), or permission filtering hiding issues from your search results.

Fix: Double-check your JQL. Common mistakes: using project names with spaces without quotes (should be project = “My Project”), using AND/OR incorrectly, or using = when you need ~. If the syntax is correct, the issue may be permission-filtered — you can only see issues you have permission to view. For Server/Data Center: administrators can re-index Jira from Administration → System → Indexing → Full Re-index. This fixes stale search results but takes time on large instances.

Integration Errors

Error 12: Jira + Slack Webhook Not Delivering Notifications

What happens: You set up a Jira → Slack notification but messages stop arriving, or arrive with significant delays.

Cause: Slack webhook URL has expired or been revoked, Atlassian’s webhook delivery is experiencing delays (check status.atlassian.com), or the Jira notification scheme isn’t configured to trigger the event type you’re watching.

Fix: In Slack, go to your app’s configuration and verify the webhook URL is still active. Generate a new one if needed, then update it in Jira’s notification settings. In Jira Cloud, go to Project Settings → Notifications and confirm the notification scheme includes the events you’re trying to catch. Check the webhook log in Jira Administration → System → WebHooks to see if webhooks are firing and what the response code from Slack is.

Error 13: GitHub/Bitbucket Commits Not Linking to Jira Issues

What happens: You include a Jira issue key in your commit message (e.g., “PROJ-123: Fixed login bug”) but the commit doesn’t appear in the Jira issue’s development panel.

Cause: The Jira-GitHub/Bitbucket integration isn’t connected to the correct repository, the commit message format doesn’t match what Jira expects, or the integration app doesn’t have access to the repository.

Fix: Verify the exact format: the issue key must appear verbatim in the commit message (case-insensitive, but no extra characters around it). Check the development tool connection in Jira Administration → Applications → Development Tools. Reconnect the GitHub/Bitbucket application and verify it has access to the specific repository. Changes can take a few minutes to sync after the initial connection.

Email & Notification Errors

Error 14: Not Receiving Jira Email Notifications

What happens: You’re a watcher on issues or the assignee, but you’re not getting email notifications when issues are updated or commented on.

Cause: Your notification preferences in Jira have email disabled, your email provider is filtering Jira emails as spam, or the project’s notification scheme doesn’t include your role for the events you care about.

Fix: In Jira Cloud, go to your Profile (avatar) → Notifications and verify email notifications are enabled for the events you care about. Check your spam folder for emails from notification@atlassian.com or jira@your-domain.com. Add the sender to your safe list. For project-specific notifications, ask your Jira admin to verify the project’s notification scheme under Project Settings → Notifications.

Error 15: Receiving Duplicate Jira Notifications

What happens: You receive multiple copies of the same Jira notification email — sometimes 2, 3, or even more copies for a single event.

Cause: You’re a member of multiple groups or roles that are all configured to receive notifications for the same event in the notification scheme.

Fix: Go to Project Settings → Notifications → Edit. For each event that’s duplicating, check how many entries are configured. If you see both “Current Assignee” AND “Group: Developers” AND “Role: Developer”, and you match all three, you get three emails. Remove redundant entries — typically “Project Role” entries are cleaner than mixing Groups and built-in roles for the same event.

Frequently Asked Questions