Skip to content

fix(jira): Catch apierror and display the project mappings anyway - #121478

Open
Christinarlong wants to merge 2 commits into
masterfrom
Christinarlong/jira-sync-status-config-null
Open

fix(jira): Catch apierror and display the project mappings anyway#121478
Christinarlong wants to merge 2 commits into
masterfrom
Christinarlong/jira-sync-status-config-null

Conversation

@Christinarlong

@Christinarlong Christinarlong commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

A bug I was able to recreate that would lead to the org config API returning an empty configData and thus not displaying any of the project mappings, despite them existing in the backend

Steps

  1. Create many project mappings, make sure they are out of order
  2. At some point here the API should break
  3. Look at the logs and see the jibberish jira sends back

The current hypothesis is that in our filter_active_projects request(when paginated-project flag is on) where we specifically query many project ids we are sending them out of order leading to the jira api breaking. Since apparently they specify that in the encoded jwt the params must be sorted.

@Christinarlong
Christinarlong marked this pull request as ready for review August 6, 2026 20:22
@Christinarlong
Christinarlong requested a review from a team as a code owner August 6, 2026 20:22
@Christinarlong
Christinarlong requested review from a team and GabeVillalobos August 6, 2026 20:27
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant