New cases are created with pre-populated Confluence activity in JIRA
プラットフォームについて: 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 は除く
問題
JIRA adds pre-populated events to the Activity stream on a newly created issue. The events are referencing pages in Confluence.
診断
環境
JIRA linked to Confluence
Diagnostic Steps
Identify the space in Confluence from where the activity is coming to JIRA
Check the space integration tools (Confluence -> affected space -> scroll down -> space tools -> if the space is back linked to the problematic JIRA project – this is where the activity comes from to Confluence
原因
This is by design. If the Confluence space is back linked to JIRA project, then JIRA cases will be able to keep track of changes occurring to existing pages in the Confluence space.
回避策
Affected articles can be moved temporarily to another space, and then copied as new back to the original Confluence space. This way JIRA will start monitoring the pages from scratch and the activities will no longer show up on new and existing cases. 
However, once the new pages are modified, the behaviour will reoccur
ソリューション
Remove the back link to JIRA project from the integration tools in Confluence (notice you will no longer be able to keep track of changes in the Confluence space from JIRA)