Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New Issue Classification Process

See original GitHub issue

Hello everyone!

We’ve reached the point where we have over 200 open issues, and want to have a good way to sort through them and to easily capture the different “classes” of issues - from first time contribution opportunities, through critical regression issues and bugs, to feature requests that can help Checkov become even more awesome!

The best and easiest way we thought of was to make a more extensive use of github labels! From (quickly 😅 ) reviewing the existing open issues, we’ve found these topics as recurring enough to have their own label:

checks - for issues around new checks, false positives in existing checks, enhancements to checks etc.
best practices - for features pertaining to acheiving best practices, example 1 example 2
output enhancement - for requests to add another output format, add fields to existing output etc. example 1
languages - for issues requesting support of more languages / extend support of existing languages. example 1 example 2 example 3
integrations - bugs and features around checkov’s integration with other tools, such as pre-commit & AWS Security Hub
graph - graph building, rendering, and supported operators for graph checks. example 1
crash - critical regression / crash issues that you run into.
skips - requests, bugs and enhancements around the skipping capabilities. example 1 example 2
parser - bugs and errors around parsing of source files. example 1
noise - issues regarding the cleanliness of the output, the verbosity of logs etc

Moreover, we would like to highly recommend adding a framework tag to denote the relevant framework that is suffering from this issue. For the framework label please use the framework name as it is defined here.

We’re open to suggestions, please feel free to share your thoughts / upvote (👍) if this sounds good to you too!

Thanks, The BC team

Issue Analytics

State:
Created 2 years ago
Reactions:4
Comments:6 (5 by maintainers)

Top GitHub Comments

2reactions

nimrodkorcommented, Dec 7, 2021

We can leverage the issue templates for this https://stackoverflow.com/questions/13829466/how-to-put-a-label-on-an-issue-in-github-if-you-are-not-a-contributor-owner/31366954#31366954

1reaction

schosterbarakcommented, Dec 7, 2021

@nimrodkor great! lets do it 😃

Top Results From Across the Web

What is Issue Classification | Helpshift

Issue classification means assigning customer service issues to the appropriate teams, agents, and channels in order to ensure the most ...

Issue Classification Schema - Skillsoft Product Documentation

Customer Support classifies each service request using two qualifiers: ... This classification schema is the cornerstone around which all support processes flow.

New Issue: Definition, How It Works in Offerings, and Example

New equity shares are often issued via an initial public offering (IPO), allowing investors to buy the stock of a previously private company...

Issue Management - Categorization & Identification

Issue identification must be an iterative process. As it progresses, more information will be gained, the issue registry will become more ...

Phase 1: Problem identification and classification

After you create the problem record, the problem classification process begins. Classification identifies relationships, urgency, assesses the impact on the ...