Skip to content

chore(jira): Add more logs/expose them better #92359

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

Merged
merged 6 commits into from
May 28, 2025

Conversation

Christinarlong
Copy link
Contributor

@Christinarlong Christinarlong commented May 27, 2025

It was harder to debug the jira assignment sync issue because we swallowed the errors

This could negatively affect our SLOs but I'd rather see all the errors first and then narrow from there,

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label May 27, 2025
@Christinarlong Christinarlong marked this pull request as ready for review May 27, 2025 21:26
@Christinarlong Christinarlong requested review from a team as code owners May 27, 2025 21:26
Copy link

codecov bot commented May 27, 2025

Codecov Report

Attention: Patch coverage is 86.66667% with 2 lines in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
src/sentry/integrations/jira/integration.py 60.00% 2 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff            @@
##           master   #92359    +/-   ##
========================================
  Coverage   87.91%   87.92%            
========================================
  Files       10217    10220     +3     
  Lines      585519   585678   +159     
  Branches    22720    22720            
========================================
+ Hits       514782   514933   +151     
- Misses      70309    70317     +8     
  Partials      428      428            

Copy link
Member

@iamrajjoshi iamrajjoshi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thank you for adding to the extras!

},
)
return
raise IntegrationFormError({"email": "Unable to find the requested user"})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IntegrationFormError is generally for misconfigured ticket/sentry app forms. is there a more relevant type of error we can raise?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the existing exceptions I see we have we could do IntegrationInstallationConfigurationError since this usually means the user either isnt verified or put a bad email/jira user.

I can narrow down the error message to be more helpful though if the user isn;t verified on sentry's side.

@Christinarlong Christinarlong enabled auto-merge (squash) May 28, 2025 18:29
@Christinarlong Christinarlong merged commit 0916bf8 into master May 28, 2025
61 checks passed
@Christinarlong Christinarlong deleted the crl/more-logging-for-jira branch May 28, 2025 18:31
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.

2 participants