-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AXON-202] Optimize Jira site resolution check at auth time #169
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug Found:
JQL doesn't update on status update any more.
https://www.loom.com/share/1629ca21ad4340648b8dd1afa522319e?sid=8a3efdfe-39c6-44f7-a35a-a5cfa82a36c9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Before the change,
JqlManager
was performing a check on the site to verify that its schema contains aresolution
field in order to construct the correct default JQL query for it.After the change, this check is performed at auth time and stored in the
DetailedSiteInfo
structure in the newhasResolutionField
field.This allows retrieving the default query for a site in constant time, and retrieving the list of all default queries (one for every site) with no latency compared to the approach before.
This change includes a backfill function in
jqlManager.ts
to handle the already-storedDetailedSiteInfo
structures without the newhasResolutionField
initialized.Tested
√ Jira Cloud auth
√ Jira DC auth
√ BitBucket Cloud auth
Test plan
https://hello.atlassian.net/wiki/spaces/AIDO/pages/4962648247/3.4.13+-+Release+Test+Plan