Clarification on changes regarding limits for Worklogs and Comments in Jira (CHANGE-1133)

[Cristina]

Regarding these changes related to limits on worklogs, comments, etc., (CHANGE-1133)

What happens with the issues that already exceed this limit and continue to increase the number of records?

[Himanshi]

Hello @Cristina , 

Welcome to the community!

This would be a good idea to consider reviewing this Blog. 

This touches base on most of the scenario by publisher or discussions in the comments. 

Specifically for your current use case : 

This won’t affect existing data for issues that are currently over the limit. But enforcement of limits will still apply for any new issue data being created on existing issues.

After considering all your feedback, we’ve decided to pause the transformation of current issues that exceed the limit for now. This means existing issue data that’s already over the limit will not be converted into another format to ensure it complies with the limit.

There are no set dates for when the transformation will resume. But we’ll give advance noticed through community posts and emails when we do, including how the transformation will be carried out.

If you have further inquiries on the same please let us know. We can check on that. 

Thank you!

[Cristina]

Hi,

I understand it, I have read the documentation of the change.

But my question is: What happens if we continue to increase the number of records  (comments, worklogs...) of an issue that already exceeds the limit?

Thank you!

[Andreas Springer _Actonic_]

@Cristina

As far as I understand it, you won't be able to increase the number of records once the limit has been reached.

For example: if an issue already contained 5000 comments, no more comments could be added.

I have just published an article summarizing the most pressing questions about this change here: https://actonic.de/en/understanding-atlassian-jira-cloud-issue-limits-and-how-to-manage-them/

By the way, it also includes a beautiful dashboard report that you can use to surface and identify the issues in your instance that are affected by these limits:

It's a custom report built in Report Builder, which means its source code can be modified to any requirement you or a client might have (more details in the article):

This report is not part of the app yet, but you will find a guide on how to add it manually in the article. Or just let me know and I will help you do that. :)

Hope this helps!