Labels schema

labels.md

Labeling issues

• status: Only one status label can be assigned at once;
  • status:accepted: The issue was valid and now is selected for development;
  • status:duplicate: The issue was already described by another issue. Must be closed referencing the original issue. Followed by close action.
  • status:invalid: The issue will be closed and not be selected for development. Followed by close action;
  • status:solved: The issue was solved by a commit and the PR was successfully merged into master/development branches. Followed by close action;
  • status:wontfix: The issue couldn't be solved for any reason which must be described in the comments section. Followed by close action;
  • status:worksforme: The issue couldn't be reproduced and everything seems normal. Followed by close action.
• priority: Only one priority label can be assigned at once;
  • priority:low: Low priority on the dev workflow;
  • priority:normal: Normal priority on the dev workflow;
  • priority:high: High priority on the dev workflow;
  • priority:critical: Maximum priority on the dev workflow.
• pending: Only one pending label can be assigned at once;
  • pending:in progress: Denotes that the issue's assigned developer is currently working on that issue;
  • pending:in review: Denotes that the issue is done and its being reviewed by someone. If the feedback went fine, the branch is ready to sent as a pull-request into development branch;
  • pending:on hold: Denotes that the issue's development was put into hold by any reason which must be described into the comment section;
  • pending:awaiting resources: Denotes that the issue's development reached a point which cannot go any further due to lack of resources. Once the resources are gathered/provided, the issue can be assigned as pending:in progress once again;
  • pending:awaiting feedback: Denotes that the issue's development reached a point which cannot go any further due to lack of information. Once this info is gathered, the issue can be assigned as pending:in progress once again;
  • pending:help needed: Denotes that the assigned developer needs the help of other developers to handle this issue in order to continue the development.
• feedback: Only one feedback label can be assigned at once. Denotes that that issue needs the feedback of other team members;
  • feedback:discussion: The issue's creator wants to start a discussion about some relevant topic;
  • feedback:question: The issue's creator wants to know something about the product/development;
  • feedback:rfc: The issue's creator needs direct comments/oppinion/position about a given topic;
  • feedback:suggestion: The issue's creator wants to suggest a new feature or change existing ones. If validated by team, will be selected for development.
• type: Only one type label can be assigned at once;
  • type:improvements: Issues that once done will improve some existent functionality/thing;
    • type:improvements:enhancements: General enhancements to existing features;
    • type:improvements:optimization: General optimization to existent code/features;
    • type:improvements:new feature: Once done will add a new feature to the final product;
  • type:issues: Denotes a problem of some sort.
    • type:issues:bug
    • type:issues:security
    • type:issuesperformance