fix(jira): Catch apierror and display the project mappings anyway - #121478
Merged
Christinarlong merged 2 commits intoAug 7, 2026
Conversation
github-actions
Bot
added
the
Scope: Backend
ceorourke
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
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.