Workflow save fails HTTP 400 "error parsing request" - 10001 bytes payload limit - team-managed proj

[Tomasz Łyczko]

Hi community,

I have a team-managed project in jira
where I cannot save any workflow changes. Every save attempt
fails with HTTP 400 "An error occurred while parsing the request".

Diagnosed details:
- Request ID: 6366271e-141c-4976-8351-2de0e86ad3d2
- Failed request Content-Length: exactly 10001 bytes
- Error body: "An error occurred while parsing the request"
- Server: AtlassianEdge, region: aws-eu-central-1

Project setup:
- Team-managed project
- 6 issue types: Epic, Bug, Spike, Story, Task, Subtask
- 7 statuses: TO DO, BACKLOG, IN ANALYSIS, READY FOR
REFINEMENT, IN PROGRESS, DONE, WON'T DO
- All issue types share one workflow
- Active sprint with 350+ issues

What happened:
Board columns and statuses disappeared. I recreated the
statuses but now the workflow payload exceeds the 10,000
byte limit and nothing can be saved.

Atlassian AI support confirmed this is a known hard-coded
limit in team-managed project architecture but the suggested
fix (decoupling issue types) risks breaking subtask-parent
relationships and is too risky with an active sprint.

Questions:
1. Can Atlassian fix the workflow configuration directly
on the backend without UI?
2. Is there a safe way to reduce payload size without
touching subtask/task relationships?
3. Is migration to company-managed possible while
preserving active sprint data?