Skip to content

[No QA] Add guidelines for working with Sentry issues #81059

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.

Sign up for GitHub

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
rlinoz merged 2 commits into from
Jan 30, 2026
Merged

[No QA] Add guidelines for working with Sentry issues #81059

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2e5c8cb
Add guidelines for working on Sentry issues in CONTRIBUTING.md
adhorodyski Jan 30, 2026
9040913
Clarify Sentry issue investigation steps in CONTRIBUTING.md
adhorodyski Jan 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions contributingGuides/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,17 @@ Basically, a bad problem statement (ie, a reverse solution statement) is written
### Posting Ideas
Additionally, if you want to discuss an idea with the open source community without having a P/S statement yet, you can post it in #expensify-open-source with the prefix `IDEA:`. All ideas to build the future of Expensify are always welcome! i.e.: "`IDEA:` I don't have a P/S for this yet, but just kicking the idea around... what if we [insert crazy idea]?".

## Working on Sentry Issues
If you have access to Sentry and are investigating an error, please **assign yourself to the Sentry issue** before starting your investigation. This helps prevent duplicate efforts where multiple contributors spend time investigating the same error independently.

When working on Sentry issues:
1. **Assign yourself** in Sentry when you start investigating an issue
2. **Link a GitHub issue** - find or create a GitHub issue for the error, then link it in Sentry using their issue tracking integration
3. **Document your findings** in the linked GitHub issue
4. **Update the Sentry issue status** when the fix is merged (mark as resolved with the version number if applicable)

This helps future investigators understand the history and current status of errors, potentially saving hours of duplicate work.

## Working on Expensify Jobs
*Reminder: For technical guidance, please refer to the [README](https://github.com/Expensify/App/blob/main/README.md)*.

Expand Down