413 Payload to Large -- Error in Jira Integration while linking flag

[Jaribeau]

How are you running Flagsmith

• [ ] Self Hosted with Docker
• [ ] Self Hosted with Kubernetes
• [x] SaaS at flagsmith.com
• [ ] Some other way (add details in description below)

Describe the bug

When a project has many flags/overrides/?, the Jira integration does not work, due to the request payload being too large.

The list of flags is shown correctly, but after selecting a flag and clicking "link", the following error is shown:

{
    "timestamp": 1706619953071,
    "path": "/central/graphql",
    "status": 413,
    "error": "Payload Too Large",
    "message": "GraphQl query and variables must not exceed 512000 bytes in size",
    "requestId": "ad93b2d2-2555788",
    "exception": "io.atlassian.graphql.gateway.http.request.RequestTooLargeException",
    "request_id": "UNKNOWN",
    "query": "unknown",
    "operation": "unspecified",
    "schema": "unspecified",
    "errorSource": "GRAPHQL_GATEWAY"
}

Steps To Reproduce

Given our company's account (i.e. with "lots" of flags, overrides, etc)

1. Click "Linked Feature Flags"

2. Select a flag to link

3. Click "link flag". Then this is shown:

Expected behavior

Flag should be linked successfully, as shown with this test project containing only one flag:

Screenshots

No response

[matthewelwell]

Hi @Jaribeau , thanks for raising this and apologies for not getting a response back to you sooner. We will take a look into this to see if we can optimise the integration to get around this. Please bear with us while we look into it and we'll update here once we have more information.

[novakzaballa]

Hi @Jaribeau, I tried to reproduce the issue by creating a test project with a similar number of flags, segments, and segment overrides, but I was unsuccessful. Could I add myself to your organisation to reproduce the issue? Also, could you please provide the project and issue IDs that raised the issue?

[Jaribeau]

Sure thing -- project is 7048.

For Jira -- it was happening with every issue.

[novakzaballa]

Thank you, I have been able to reproduce the issue and I'm investigating further. I will return with an answer as soon as possible.

[matthewelwell]

@dabeeeenster @novakzaballa I think this is just waiting on a new releae of the JIRA application, can you guys arrange this?

[dabeeeenster]

What's in main is what is live right now AFAIK - what PRs need to go live @novakzaballa ?

[novakzaballa]

There's a PR that needs approval from @matthewelwell