Notifications Are Issued for Incorrect Jira Issues


アトラシアン コミュニティをご利用ください。


プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

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.

*Fisheye および Crucible は除く



  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.

最終更新日 2022 年 4 月 29 日


Powered by Confluence and Scroll Viewport.