"A number of comments for issue has breached the limit of 1000" Warning

Aboubacar Sambare
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 15, 2024

Hello community,

We are encountering a warning stating:
“A number of comments for issue has breached the limit of 1000, the comment was added. Issue key: XXXX-123344, issue comments count: 9514, comment author: XXXX, logged-in user: XXXXX.”

However, for the specific issue key in question, there are only 5 comments, and the issue was closed 2 years ago.

Could anyone explain why this warning is appearing and under what conditions it occurs?

Jira version: 9.12.x 

How can I resolve it?

Thank you in advance for your help!

1 answer

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 15, 2024

HI @Aboubacar Sambare 

Welcome to the community.

This seams to fix issue JRASERVER-72612

Check the links on this Atlassian issue. Safe Guards have been set in place in the software, your are able to disable these,

moderating-user-group-activity-with-safeguards 

Aboubacar Sambare
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 15, 2024

Thanks for your response

We are using Safeguard, so we just need to disable it for that user?

This warning is for issues closed two year ago. Do you know why?

 

 

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 15, 2024

HI @Aboubacar Sambare 

No its no for that user, for the system. These settings are system wide.

No I can't tell you why, you could check the logs or contact Atlassian Support in the case.

Ask them why this is happening on an old issue, it seems like an indexing issue.

So you could re-build your index.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
9.12
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events