Decide on a reasonable default labelset #10

New Issue

AliasAlreadyTaken · 2024-06-03T21:28:35+02:00

AliasAlreadyTaken commented

2024-06-03 21:28:35 +02:00

Maybe we could look at other features the git provider brings with it and use them as well - maybe even define a workflow :P

AliasAlreadyTaken commented

2024-06-04 02:43:25 +02:00

Labelset

type: What kind is that issue?

type/bug : For errors or problems with existing code
type/enhancement : For suggestions and improvements of existing functionality
type/documentation : For missing, incomplete or additional documentation
type/security : For vulnerabilities both from and to this code
type/task : For maintenance, chores or background works
type/feature : For larger additions not yet in the plans
type/invalid : For non-issues, spam or accidental submissions
type/other : For issues that do not fit anywhere else

priority: What order do we need to address the issue in?

prio/critical : For crashes, data loss or similar severe problems
prio/high : For immediate attention but without the risk
prio/blocker : Prevents delivery, update or someone else's works
prio/urgent : Needs to be addressed first, in a timely fashion
<-- prio/medium is default, all issues that do not have a priority are considered medium
prio/low : Can wait until resources are available to address this

source: Where does the issue originate from?

source/code : Relates to the source code
source/media : Relates to art, models, textures or other media
source/performance : Relates to lag, inefficient code or general speed of execution
source/license : Relates to problems with legalities or law
source/design : Relates to user interface or GUI
source/integration : Poses a problem only together with other non-buggy components
source/external : The problem arises only together with outside code
source/other : Source is not in any other category

step: What status is the issue in?

step/review : We are in the process of deciding how to solve this
step/work : Someone is actively developing on this
step/question : There are information missing, a repro needs to be found or research to be done
step/verify : Some information about this issue needs to be confirmed
step/test : QA needs to verify the solution works as intended
step/ready : This issue is ready for delivery
step/blocked : There is a roadblock preventing us from taking the next step which needs to be resolved first

result: How was the issue resolved?

result/fixed : The issue is fixed
result/wontfix : The issue will not be fixed
result/notabug : The issue turned out not to be a bug at all
result/notourbug : The issue is not in our code, but somewhere else
result/norepro : The issue cannot be reproduced
result/duplicate : This is a duplicate. Please link to the original
result/deferred : This issue cannot be dealt with now, but will be at a later time
result/other : Some other result that does not fit in any other category

Labelset type: What kind is that issue? type/bug : For errors or problems with existing code type/enhancement : For suggestions and improvements of existing functionality type/documentation : For missing, incomplete or additional documentation type/security : For vulnerabilities both from and to this code type/task : For maintenance, chores or background works type/feature : For larger additions not yet in the plans type/invalid : For non-issues, spam or accidental submissions type/other : For issues that do not fit anywhere else priority: What order do we need to address the issue in? prio/critical : For crashes, data loss or similar severe problems prio/high : For immediate attention but without the risk prio/blocker : Prevents delivery, update or someone else's works prio/urgent : Needs to be addressed first, in a timely fashion <-- prio/medium is default, all issues that do not have a priority are considered medium prio/low : Can wait until resources are available to address this source: Where does the issue originate from? source/code : Relates to the source code source/media : Relates to art, models, textures or other media source/performance : Relates to lag, inefficient code or general speed of execution source/license : Relates to problems with legalities or law source/design : Relates to user interface or GUI source/integration : Poses a problem only together with other non-buggy components source/external : The problem arises only together with outside code source/other : Source is not in any other category step: What status is the issue in? step/review : We are in the process of deciding how to solve this step/work : Someone is actively developing on this step/question : There are information missing, a repro needs to be found or research to be done step/verify : Some information about this issue needs to be confirmed step/test : QA needs to verify the solution works as intended step/ready : This issue is ready for delivery step/blocked : There is a roadblock preventing us from taking the next step which needs to be resolved first result: How was the issue resolved? result/fixed : The issue is fixed result/wontfix : The issue will not be fixed result/notabug : The issue turned out not to be a bug at all result/notourbug : The issue is not in our code, but somewhere else result/norepro : The issue cannot be reproduced result/duplicate : This is a duplicate. Please link to the original result/deferred : This issue cannot be dealt with now, but will be at a later time result/other : Some other result that does not fit in any other category

AliasAlreadyTaken commented

2024-06-04 03:36:03 +02:00

Here's a nice guide towards issue lifecycle: https://www.shakebugs.com/blog/issue-tracking-workflow/

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/yl_template#10