Sentry Entegrasyonu
The Sentry integration connects production error tracking with project management. When Sentry detects an error, you can link it to an existing SetGet work item or create a new one. Resolving the issue on either side resolves it on the other, keeping your error tracker and task board in sync.
Yetenekler
| Feature | Description |
|---|---|
| Link Sentry issues to work items | Associate production errors with the work items responsible for fixing them |
| Create work items from Sentry | Generate a new SetGet work item directly from the Sentry issue page |
| Bidirectional state sync | Resolving in Sentry marks the work item as Done; completing the work item resolves the Sentry issue |
| Error context in SetGet | View Sentry error details (title, frequency, last seen) on the linked work item |
Onkosullar
- A Sentry account with Admin or Manager access to the organization.
- Admin or Owner role in your SetGet workspace.
- At least one Sentry project with active error monitoring.
Kurulum adimlari
Adim 1 -- Baglanma Sentry
- In SetGet, go to Settings > Integrations.
- Find the Sentry card and click Connect.
- SetGet redirects you to Sentry's authorization page.
- Select the Sentry organization you want to connect.
- Click Accept.
- You are redirected back to SetGet. The Sentry card shows "Connected" with your organization name.
Adim 2 -- Map Sentry projects to SetGet projects
Mapping is optional but improves the workflow. When a Sentry project is mapped to a SetGet project, new work items created from Sentry automatically go to the right project.
- In SetGet, go to Settings > Integrations > Sentry.
- Click Map Projects.
- Her Sentry project, select the corresponding SetGet project from the dropdown.
- Click Save.
| Sentry project | SetGet project |
|---|---|
frontend-web | Web |
api-service | API |
mobile-ios | Mobile |
Adim 3 -- Configure state sync
State sync maps Sentry issue states to SetGet work item states.
| Sentry state | Default SetGet state | Changeable |
|---|---|---|
unresolved | In Progress | Yes |
resolved | Done | Yes |
ignored | Cancelled | Yes |
Customize in the integration settings under State Mapping.
Entegrasyonu kullanma
Bir Sentry sorununu mevcut bir is ogesine baglama
- In Sentry, open the issue you want to link.
- In the sidebar, find the SetGet section.
- Click Link to existing work item.
- Search for the work item by title or identifier.
- Click Link.
The Sentry issue page now shows the linked work item, and the SetGet work item shows the linked Sentry issue in its Links section.
Sentry'den yeni bir is ogesi olusturma
- In Sentry, open the issue.
- In the SetGet section, click Create work item.
- The title is pre-filled from the Sentry issue title. Modify if needed.
- Select the target project, state, priority, and assignee.
- Click Create.
The new work item includes a link back to the Sentry issue and error context (error type, frequency, last occurrence).
SetGet'te Sentry baglamini goruntuleme
On a linked work item, the Links section shows:
- Sentry issue title
- Error count (total occurrences)
- Last seen timestamp
- Direct link to the Sentry issue page
- Current Sentry state (unresolved/resolved/ignored)
Cift yonlu durum senkronizasyonu
When state sync is enabled:
- Sentry resolved -- the linked SetGet work item moves to the mapped state (default: Done).
- SetGet work item completed -- the linked Sentry issue is marked as resolved.
- Sentry regression -- if a resolved Sentry issue regresses (reoccurs), the SetGet work item moves back to the mapped unresolved state.
WARNING
Regression detection only works if the Sentry issue triggers a new event after being resolved. One-time errors that recur will reopen the linked work item.
Kullanim senaryolari
| Scenario | Workflow |
|---|---|
| Bug triage | Link incoming Sentry issues to work items, assign to engineers, track resolution |
| Release validation | After a deploy, check linked Sentry issues for regressions |
| Customer support | Support team finds related Sentry issues, links to work items, tracks fix progress |
| Sprint planning | Pull high-frequency Sentry issues into the current cycle as work items |
Entegrasyonu yonetme
View linked issues
Go to Project Settings > Integrations > Sentry to see a list of all linked Sentry issues and their current sync status.
Unlink a Sentry issue
On the work item, click the x next to the Sentry link in the Links section. This removes the link but does not delete the Sentry issue or the work item.
Disconnect Sentry
Go to Settings > Integrations > Sentry and click Disconnect. This revokes the OAuth token and removes all project mappings. Existing links are preserved as static references but stop syncing.
Sorun giderme
| Problem | Cause | Solution |
|---|---|---|
| SetGet not appearing in Sentry sidebar | Integration not installed | Complete setup in Settings > Integrations |
| State not syncing | State mapping misconfigured | Review and update state mapping |
| Wrong project selected | Project mapping missing | Map Sentry projects to SetGet projects |
| Regression not reopening work item | State sync paused | Check integration settings |
Uyari kurallari
You can configure Sentry alert rules to automatically create SetGet work items when certain conditions are met:
| Alert condition | Action |
|---|---|
| New issue detected | Create a work item with High priority |
| Issue frequency exceeds threshold | Create a work item with Urgent priority |
| Issue regresses | Reopen the linked work item |
Configure alert-to-work-item rules in Sentry under Project > Alerts > SetGet action.
TIP
Combine Sentry alert rules with SetGet automations to auto-assign incoming bug reports to the on-call engineer.
Birden fazla Sentry projesi
You can map multiple Sentry projects to different SetGet projects within the same workspace. This is common for teams that maintain separate Sentry projects for frontend, backend, and mobile while tracking all work in a single SetGet workspace.
| Architecture | Sentry setup | SetGet mapping |
|---|---|---|
| Monolith | 1 Sentry project | 1 SetGet project |
| Microservices | N Sentry projects | N SetGet projects (one per service) |
| Multi-platform | 3 Sentry projects (web, iOS, Android) | 1-3 SetGet projects (your choice) |
Guvenlik
- OAuth tokens are encrypted at rest and stored server-side only.
- Sentry webhook payloads are verified before processing.
- The integration does not access Sentry event payloads (stack traces, user data) beyond metadata (title, count, timestamps).
- The minimum required Sentry scope is
project:readandevent:read. - You can revoke access from Sentry at Settings > Developer Settings > Integrations.
Sik sorulan sorular
Can I link one Sentry issue to multiple work items?
No. Each Sentry issue can be linked to one work item at a time. To track a Sentry issue across multiple work items, create a parent work item and link the Sentry issue to it.
Does the integration import Sentry event data (stack traces)?
No. Only metadata (title, event count, last seen timestamp, state) is synced. Stack traces and user data remain in Sentry.
What happens if I resolve the same issue in both Sentry and SetGet simultaneously?
Both actions are processed. The final state reflects the last sync event. In practice, this results in both being resolved, which is the expected outcome.