Hello there,
I can't access any issue for any project after rename the key of one project. I changed back the project key and re-index, restart server. I also tried to create a project and delete it. The integrety checker is good.
The error message is "Project Does Not Exist:
The project or issue you are trying to view does not exist. Try browsing for projects.
If you think this message is wrong, please contact your Jira administrators."
Please help to throw some idea on this.
Thanks,
Bob
Hello @Bob Yang,
On the surface, it sounds like you just got removed from the project permissions during the updates and would only need to add yourself to the "Browse Project" project level permission to gain view access to the issues. But as you noted trying to create and delete a project I am hoping that the one you wanted to keep was not deleted by mistake.
First, check the project permissions as covered in the follwoing document, by logging in as a global admin and modifying the project permission:
Next, I would say go to the database and run a select on you projects table to get a count on the issues in there to verify they still exist in the database, here is a quick EXE on a test instance I just created noting the pcounter column is the number of issues in the project:
(NOTE: Syntax is for PostgreSQL)
jiradb=> select * from project ;
id | pname | url | lead | description | pkey | pcounter | assigneetype | avatar | originalkey | projecttype
-------+--------+-----+---------------+-------------+--------+----------+--------------+--------+-------------+-------------
10001 | Init | | JIRAUSER10000 | | INIT | 1 | 3 | 10324 | INIT | software
10000 | asdf | | JIRAUSER10000 | | ASDF | 10 | 3 | 10324 | ASDF | software
10100 | qwerty | | JIRAUSER10000 | | QWERTY | 6 | 3 | 10324 | QWERTY | software
(3 rows)
If they are indeed gone than a restore to the last known good backup would be the only way to recover them, I would recommend if this is the case, that you set up a test environment as covered here:
Gather an XML backup of your JIRA instance. Even if you did not manually create one Jira will automatically create one by default unless it was turned off previously, If the backup was created you can find the most recent one of these backups in the filesystem of the Jira server. By default this is saved in <jira-home>/export/ folder you can then import your previous data into a staging server and then look into migrating the project data from staging back to production as covered in:
Regards,
Earl
Hi Earl,
I noticed that one system plugin was disabled accidently. After enabling that plugin, it works correctly now.
Thank you all the same.
Bob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bob,
Can you pls let me know which plugin you have enabled? I am also getting the same issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.