Resolve Issues in the Next Release
A 3-step recipe with Sentry. We can help you get access.
Recipe · 3 steps
Resolve Issues in the Next Release
with Sentry
Cut a release and resolve the top unresolved issue in that next release.
- Create the release record for deployment and source-map tracking, scoped to the supplied project slugs.
- List the organization's unresolved issues by frequency to find the top candidate to resolve in the new release.
- Mark the selected issue as resolved in the next release so it stays resolved unless the error recurs after this deploy.
What you'll need to have ready
- organizationSlug: The organization slug that owns the release and issues.
- version: The release version string (e.g. a git SHA or semver tag).
- ref: Optional git ref (branch or tag) for the release.
- projects: List of project slugs the release applies to.
- query: Sentry query used to find issues to resolve.
For your developer
Arazzo workflow sentry:resolve-issues-in-release, 3 operations: createRelease → listOrganizationIssues → updateIssue. Specs on APIs.io.