Feature request: A way to differentiate errors in the Error tracking list
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Feature request
Is your feature request related to a problem?
In the Error tracking list, I could have different issues, e.g, related to API calls, Typescript, some specific feature, some specific library.
I need to have a way to differentiate and mark them, and probably filter by them (less important)
Describe the solution you'd like
I would love to have something like tags/labels as Jira or Linear have. And then the user can create these tags and assign them to errors. And probably group them somehow
Describe alternatives you've considered
Additional context
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. Begin with the Error tracking list and clarify the desired tag creation, assignment, filtering, and grouping behavior; done means users can differentiate errors with user-defined tags.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100