JIRA Documentation

JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation


Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »


Ordinarily, JIRA uses each issue key once and once only within a project. If you need to reset the numbering (such as when deleting a bunch of bogus issues created via email), there is no way to reset the numbering through the web interface. If the number is reset mistakenly, JIRA will increment the issue key until it finds the next available key. This can be time consuming for large instances.


One potential cause of this problem is this known issue where project description updates can reset the project counter:



Other than simply adding a new issue and letting the system check for existing issues, the only way to reset the numbering for a project is to perform a direct database query.

  1. Stop JIRA
  2. Given the name of the project ("Project Name" in my example), you'll need to run a query like the following to view the current counter settings:
  3. You will see output like the following:
      id   |         pname         | url |   lead    |                     description                     | pkey  | pcounter | assigneetype
     10000 | Project Name          |     | admin     |                                                     | PROJ  |        9 |            3
  4. Run a query like the following to reset the value per project:
  5. Alternatively you can reset the value across all projects:
    1. MySQL:
    2. PostgreSQL:
  6. Start JIRA

Additional Information




Regular Expression

ERROR \[atlassian.jira.project.DefaultProjectManager\] Existing issue found for key

Article ID


  • No labels