Better Issue Tracking
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
@agcolom requested that I open a single issue with all requests.
- Make the tracking code public
- Monitor all repositories
- Track pull requests and issues
- Track opens and closes, not just total open count
- Track average age
- Push the data into Splunk
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 reviewing the repository and the checklist to identify the existing tracking implementation. Done would require an agreed scope and verified support for repository, pull-request, issue, open/close, age, and Splunk reporting requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100