Jira Cloud Limits 2025: Worklogs Now 10k – What Admins Must Do Next
Atlassian has updated its guidance on Jira Cloud work item (issue) limits for 2025. The biggest change: the worklog cap is now 10,000 per issue, and Atlassian has consolidated the rules into a single “work item field limits” document.
In Jira Cloud, each issue allows 5,000 comments, 10,000 worklogs, and 2,000 each for attachments, issue links, and remote links.
TL;DR – 2025 highlights
- Worklogs: limit is 10,000 per issue (raised vs. older 5k references).
- Docs refresh: Atlassian consolidated “work item field limits” and the “too many <X>” remediation pages.
- Display caps still matter: company-managed boards/backlogs show up to 5,000 items; Jira Work Management boards show up to 3,000.
Need the full explanation of every limit? Read our evergreen guide.
What’s new or newly clarified in 2025
- 10,000 worklogs per issue: hitting the cap triggers optimization (extra worklogs moved to a new, linked issue).
- Consolidated “work item” terminology: Atlassian docs increasingly use work item where many teams still say issue.
- Behavior at limits spelled out: extra comments/remote links exported to CSV and attached; extra links/worklogs moved to a new linked issue; excess attachments bundled into an archive.
| Item | 2024 | 2025 | What Jira does at the cap |
|---|---|---|---|
| Worklogs | 5,000 (older refs) | 10,000 | Moves extras to a new linked issue |
| Comments | 5,000 | 5,000 | Exports extras to CSV & attaches |
| Attachments | 2,000 | 2,000 | Bundles extras into an archive |
| Issue links | 2,000 | 2,000 | Moves extras to a new linked issue |
| Remote links | 2,000 | 2,000 | Exports extras to CSV & attaches |
What hasn’t changed
- Comments: 5,000 per issue.
- Attachments: 2,000 per issue (UI switches to list view at >150 attachments).
- Issue links: 2,000 per issue (excludes child issues/sub-tasks).
- Remote links: 2,000 per issue.
- Per-file size (admin-configurable): default 1 GB, max 2 GB; site storage: Free 2 GB, Standard 250 GB, Premium/Enterprise Unlimited (per product).
Why this matters
- Silent failures & split data: once an item hits a cap, Jira blocks or relocates new entities. Teams may assume data is missing unless they check the linked “overflow” issue.
- Board blindness: filters that return >5,000 (or >3,000 in JWM) mean part of the backlog won’t be visible.
- Migrations: oversize issues are auto-adjusted post-import; if you don’t pre-check, your data layout can change unexpectedly.
Your 60-minute admin checklist
- Add near-limit alerts: create an Automation rule to comment/label when an issue approaches 80% of caps:
- Comments: 4,000
- Worklogs: 8,000
- Attachments: 1,600
- Issue links / Remote links: 1,600
- Right-size boards: adjust JQL so each board/backlog returns <5,000 (or <3,000 for JWM) items.
- Rotate heavy “catch-all” items: split quarterly/annual mega-tickets before they accumulate thousands of comments/worklogs.
- Attachment policy: prefer links to Drive/SharePoint/Confluence for large assets; set a sensible per-file cap.
- Migration pre-flight: run a report to flag issues close to any cap; fix them before moving to Cloud.
For the full background on each limit and remediation options, see our comprehensive guide to Jira Cloud issue limits.
Editor’s note: This is a news-style update. For a deep, always-on reference (with examples and troubleshooting), use our full guide to Jira Cloud issue limits.