Jira Error Code ISSUE_DOES_NOT_EXIST: How to Fix It
Easy 5-15 minutes Medium Severity
Verified June 2026
- Error Code
- ISSUE_DOES_NOT_EXIST
- Brand
- Jira
- Product Type
- productivity
- Severity
- Medium
- DIY Difficulty
- Easy
- Estimated Fix Time
- 5-15 minutes
Ad
Tools You'll Need
- Web browser
- Jira account with appropriate permissions
How to Fix Error Code ISSUE_DOES_NOT_EXIST
-
Verify the Issue Key Format
-
Check Your Project Permissions
-
Search for the Issue Using Advanced Search
-
Check if the Issue Was Moved or Renamed
-
Verify Issue Hasn't Been Deleted
-
Clear Browser Cache and Cookies
-
Try Accessing from Different Browser or Device
Ad
When to Call a Professional
Contact your Jira administrator when you need access to specific projects, when issues may have been accidentally deleted and need recovery from backups, or when you suspect there are broader permission or configuration issues affecting multiple users.Frequently Asked Questions
Why do I get ISSUE_DOES_NOT_EXIST for an issue I created?
This usually happens when the issue was moved to a different project you don't have access to, or when project permissions were changed after you created the issue.
Can I recover a deleted Jira issue myself?
No, only Jira administrators can recover deleted issues from system backups. Regular users cannot restore deleted issues on their own.
How do I know if an issue was moved to another project?
Check your email notifications, the project's activity stream, or ask your team members. Moved issues typically generate notifications to relevant users.
What does it mean when I can see some issues but not others in the same project?
This indicates you have limited permissions in that project. Some issues may be restricted based on security levels, issue types, or custom permission schemes.