Issue Summary

The Jira Change Log blueprint fails during page creation when it is used without a Fix Version or other sufficiently restrictive scope and the selected Jira project contains a large number of issues.

The customer project contains approximately 3,980 issues. The issue was independently reproduced locally by creating 5,000 Jira issues and then creating a Confluence page using the Jira Change Log blueprint with no Fix Version selected.

The failure occurs during blueprint request processing, before the page is successfully created. Removing the macro after creation is therefore not possible and does not resolve the issue.

The exception occurs while Confluence deserializes the blueprint request context:
 

com.fasterxml.jackson.databind.JsonMappingException: Unexpected end-of-input: was expecting closing quote for a string value 
... 
CreateBlueprintPageRestEntity["context"] 
... DefaultRequestStorage.retrieveRequest

The underlying exception is reported at:

com.fasterxml.jackson.core.io.JsonEOFException Unexpected end-of-input: was expecting closing quote for a string value line: 1, column: 100001

The exact 100,001 column position is consistent with the serialized blueprint context being truncated at approximately 100,000 characters. The exact storage/configuration limit and owning component require confirmation.

Steps to Reproduce

1. Set up Confluence Data Center 10.2.11 and a connected local Jira instance.
2. Configure a working Jira application link between Jira and Confluence.
3. In Jira, create a project with a large number of issues. The issue was reproduced with 5,000 Task issues created through the Jira bulk issue REST endpoint in batches of 50.
4. Open Confluence and select the Jira Change Log template/blueprint.
5. Configure the blueprint for the Jira project.
6. Leave Fix Version unset so that the blueprint attempts to include all matching project issues.
7. Submit the blueprint to create/save the page.
8. Review the Confluence application log.

Expected Results

1. The blueprint should handle a large issue set safely by either:
2. Generating the Change Log successfully using pagination/chunking; or
   • Validating the result size before page creation and displaying a clear, actionable error; or
   • Requiring a bounded filter/scope before allowing page creation.
3. If the blueprint is not designed to support an unbounded project-wide result set, the UI should communicate this limitation before the request is submitted.

Actual Results

1. Page creation fails when the generated Jira issue data exceeds approximately 100,000 characters.

The request fails while Confluence is deserializing the blueprint context, with:

JsonEOFException: Unexpected end-of-input: was expecting closing quote for a string value at line 1, column 100001

No usable page is created. The failure occurs before the user can remove the generated macro/content.

Workaround

1. Use a bounded scope when creating the Change Log, such as a Fix Version or another filter supported by the blueprint.
2. Split the project issues across multiple Change Log pages instead of generating one page for the entire project.
3. Narrow the Jira query by issue type, component, label, date range, or another supported criterion.
4. If a full project-wide list is required, consider using a blank Confluence page and adding Jira issue content in smaller, separately filtered sections. This should not be expected to reliably support all 3,980–5,000 issues in one generated block.
5. There is currently no known supported configuration for increasing the apparent 100,000-character boundary