Upcoming changes: Issue transformations

[#1]

This post continues our previous updates, in which we introduced issue limits for Jira cloud to improve performance and reliability. We rolled out the issue limits for comments, attachments, linked issues, remote links and worklogs. Additionally, to help monitor and manage the data, we introduced new tools

1. Admins can get the list of issue IDs that are approaching the limit or over the limit using the Get Issue Limit Report API.

2. Bulk move and Bulk delete APIs for worklogs to keep worklogs under the 10K limit

Now, for our final phase, Issues which continue to exceed the limit would be automatically 'transformed' to get them below the defined limits.

---

What is transformation?

Transformation is a Jira-led process, only for Issues over the limit (see limits here). In transformations, a data entity, eg, comments, would be changed into a different format, eg, a CSV file and the excess data in the original format would be deleted. (shared in detail below).

When would the transformations happen?

Transformations would automatically trigger starting 12th May’25. To ensure minimal disruption, we suggest using the tools to move or clean the data before 12th May’25.

Let’s look into the transformation of each entity.

---

Comments transformations

If an issue has over 5,000 comments—let's say 5,400 comments—the additional 400 comments will be converted into a CSV file as an attachment to the issue. Furthermore, these 400 excess comments will be automatically removed, leaving only the attached CSV file associated with the issue.

---

Attachments transformations

If an issue has over 2000 attachments—let's say 2400 attachments—the additional 400 attachments will be converted into a ZIP file as an attachment to the issue. Furthermore, these 400 excess attachments will be automatically removed, leaving only the attached ZIP file.

---

Worklog transformations

If an issue has over 10,000 worklogs—let's say 10,400 worklogs—the additional 400 worklogs will be moved to a new issue (a copy of the original issue). Furthermore, these 400 excess worklogs on the original issue will be automatically removed. It is worth highlighting that the new issue will be linked to the old issue to make the tracking simpler. 

---

Remote links transformations

If an issue has over 2000 remote—let's say 2400 remote—the additional 400 remote links will be converted into a CSV file as an attachment to the issue. Furthermore, these 400 excess remote will be automatically removed, leaving only the attached ZIP file.

---

Issue links transformations

If an issue has over 2000 issue links—let's say 2400 issue links—the additional 400 issue links will be moved to a new issue (a copy of the original issue). Furthermore, these 400 excess issue links on the original issue will be automatically removed. It is worth highlighting that the new issue will be linked to the original issue to make the tracking simpler. 

---

Post transformation validation

---

FAQs

Will the transformations impact migrators?

Yes, transformations will trigger as soon as a customer migrates to cloud. To avoid surprises, we will ensure communicating these limits at step during migrations.

We don’t have any issues over the limit, will transformations impact us?

No, transformations would trigger only for issues over the limit. You can check Get Issue Limit Report API

[Lucas Modzelewski _Lumo_]

@Apoorv Aggarwal please check the Loom video settings, as we are unable to view it or request access.

[Matt Doar _Adaptavist_]

Very useful details about the transformers, thanks

[Jiayi Litten]

Hello everyone, The Loom videos have been updated to be publicly accessible. Thank you!