Upcoming changes: Introducing per issue limits for list fields in Jira Issues

[Andreas Springer {Actonic}]

@ting_t_chi No, the rollout for worklog limits has been postponed to August.

[Andreas Springer {Actonic}]

By the way, I have published an article outlining the current state of this change here: https://actonic.de/en/understanding-atlassian-jira-cloud-issue-limits-and-how-to-manage-them/

Also included in the article is a way to quickly identify and surface issues that are affected by these limits right on your dashboard:

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 can be helpful to someone!

[Jennifer Fölster]

@Shiraine LiuIs there any update on the time schedule, as the mentioned due date is coming closer?

Did you elaborate any solution with Tempo so far?

[Martin Maida]

I have a issue related to the WORKLOGS time because we use a CARD (ticket) to count Vacation time and in 7 months we reach 4600 Worklogs there.

Do you expect to increase this threshold? If not, how can I remove old worklogs ( from the beginning of the year) ?

[Apoorv Aggarwal]

@Susan Hauth _Jira Queen_ thanks for your feedback. Atlassian has increased the initially proposed work log limits and built relevant tooling to mitigate the risk of breaching these limits. Please find the updated solution here: https://community.atlassian.com/t5/Jira-articles/Introducing-Bulk-Move-and-Bulk-Delete-Worklog-APIs/ba-p/2792183 

[Apoorv Aggarwal]

@Jennifer Fölster we've extend the timeline for enforcing the worklog limits until December'2024. Please find the latest updates here: https://community.atlassian.com/t5/Jira-articles/Introducing-Bulk-Move-and-Bulk-Delete-Worklog-APIs/ba-p/2792183

[ting_t_chi]

Hi @Apoorv Aggarwal ,
Thank you for the update. We found that API does not allowing us to delete/move/add approved timesheet. Any solution for that? 

[Apoorv Aggarwal]

@ting_t_chi if you're using Tempo timesheets, we recommend using the solutions and API provided by them. The subsequent community post includes the link to their solutions. 

[Daniel Menard]

I'd like to commend @Shiraine Liu, @Apoorv Aggarwal and the Atlassian team for listening to user feedback on this issue and coming up with a workable solution for moving worklogs with Tempo. I haven't started using the new tools yet, but I feel much more confident that there is a path to resolve this without a major impact to our business.

[Apoorv Aggarwal]

Hey @Stuart Nealis 

You can now delete up to 5,000 worklogs at a time using the new Bulk Delete API.

Here's the new community post on the latest updates https://community.atlassian.com/t5/Jira-articles/Introducing-Bulk-Move-and-Bulk-Delete-Worklog-APIs/ba-p/2792183 

[avyas]

Hi,

We generate reports using Jira APIs in Power BI and eazyBI, while also using Tempo for logging timesheet. I would like to understand how issue limits could affect our operations in cases mentioned below:

1. What happens if an issue crosses a certain limit?

   • For example, if an issue has 2,540 comments, will it stay as is? Can additional comments still be added, or is there a maximum?
   • Will Jira prompt us to create a new issue to continue? If so, is there a quick way to create a new issue that replicates the details of the one that has reached its limit?

2. Is there a way to query issues to identify those approaching or exceeding limits?

   • We’d like to query Jira for issues that are nearing or have surpassed limits on specific parameters to proactively manage them.

3. Are there limits on issue history?

   • Will the issue history be restricted to a certain number of entries?

4. Internal issues used company-wide often surpass limits faster.

   • Time is frequently logged to internal issues in Tempo, which are used across the company and can exceed limits more quickly than other issues. What steps can we take to manage this?

It will be great help to get answers as per latest updates to my queries.

Best regards, 

Anushree 

[Symeon Brown]

"Linked issues are limited to 2000 per issue. This does not include child issues."

What does it mean that this limit does not include child issues? I have a parent issue currently that has more than 2000 child issues and is throwing an error "ISSUE_LINKS_PER_ISSUE_LIMIT_EXCEEDED: 2000"

It would seem that child issues are not exempt. Or am I misunderstanding the limit?