Allow configuring Azure DevOps integration scopes
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 22h 21m
- Merged PRs (30d)
- 586
Description
### Problem Statement
Filing on behalf of user in this ticket: https://sentry.zendesk.com/agent/tickets/161036
Currently there's no way to configure scopes granted to Sentry when installing the integration. For users who do not want to setup features such as code mapping, and just want to use more basic features such as issue linking, we can consider being more lenient in required permissions.
### Solution Brainstorm
provide some way to configure scopes
### Product Area
Settings - Integrations
Contributor guide
Research direction
Start in the Settings - Integrations area and trace the Azure DevOps installation flow. Review the requirements described in Zendesk ticket 161036 and determine how configurable scopes should relate to features such as code mapping and issue linking. Done should be a decided, documented scope configuration design, with the relevant integration behavior and permissions covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100