Notifications Are Issued for Incorrect Jira Issues

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


Symptoms include:

  1. Gaps in new issue numbers (for example ABC-5 then ABC-9)
  2. Users create a Jira issue via email but in Jira it doesn't exist
  3. Users create a Jira issue via email but in Jira it is the wrong issue


More than one Jira instance is running, with the same set of projects, same base URL, and with the same email services listening to the same POP3 accounts. One of the instances is actually running at the base URL. One is running elsewhere.

Generally this happens with a development or test instance, created by a data export.


Turn off the non-production Jira instance, or disable email fetching in it by setting the following startup properties:

    -Datlassian.mail.fetchdisabled=true -Datlassian.mail.senddisabled=true

See Setting Properties and Options on Startup for more information.

Last modified on Apr 29, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.