Issues with too many work logs

This insight checks if any of your issues exceed the limit of work logs.

Why is there a limit?

Jira Cloud limits the number of work logs per issue, because adding unlimited entities often results in unusually large and complex data shapes, which in turn causes reliability and performance problems.

Migrations are exempted from this limit so they’re not blocked. However, after you migrate, we’ll automatically modify your issues, optimizing work logs above the limit in the following way:

1. We’ll remove excess work logs from your issue.

2. We’ll move them into a new issue and link it to the original one.

3. We’ll set the author of the moved work logs to the reporter of the original issue.

4. You won’t be able to add new work logs above the limit.

What’s the recommendation?

For active issues where you still add work logs, you can use the ideas below to reduce their number. However, it might be easier to let us remove excess work logs after you migrate and start fresh in new issues.

Delete extra work logs RECOMMENDATION

Jira doesn’t have an easy way to delete work logs in bulk. Below, we’ve added some ideas so you can check which one works for you.

Identify affected issues with SQL query

When viewing this recommendation from the dashboard, copy the provided SQL query and run it on your database.

The SQL query returns:

• Issues with over 10,000 work logs

• Work log count for each issue

Option 1: Delete extra attachments with Jira automation (Data Center or Cloud)

The following article on Community describes how to build a Jira automation rule to delete all work logs in bulk.

Delete work logs with Jira automation

Option 2: Delete extra attachments with API

The following pages link to APIs used to delete work logs.

1. Get issue link ID from an issue. To do this, you need to specify fields as issuelinks: GET Get issue

2. Delete an issue link based on its ID: DEL Delete issue link