Ability to test issue ownership rules
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
Adding on behalf of a customer:
I'd like to be able to verify the accuracy of our ownership rules/auto-assignment before we start alerting engineers.
Solution Brainstorm
Some way to verify accuracy of ownership rules without actually alerting end users.
I think this is a good point, it's a good idea to have some kind of dry-run mode so we can verify who an assignment would go to, without actually pinging a bunch of random people!
Product Area
Issues
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the ownership-rule and auto-assignment implementation, then define the dry-run behavior and its expected output before determining how it can be tested without alerting users.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100