Labels

• 3rd-part-compatibilities

  Issue or feature related to a compatibility with a 3rd party product.
• accessibility

  Accessibility improvements or issues.
• bug

  This label could be used to identify issues that are caused by a defect in the product.
• customer report

  Indicates the request came from a customer.
• dependencies

  Pull requests that update a dependency file
• doc-needed

  This issue requires documentation updates or additions once it has been completed.
• documentation

  Improvements or additions to documentation
• duplicate

  This issue or pull request already exists.
• enhancement

  Request to improve or optimize an existing feature or functionality in the project
• good first issue

  This could be used to identify issues that are suitable for people new to the project to work on.
• help wanted

  This can be used to identify issues that the maintainers of the project would like some help with.
• invalid

  Could be used to identify issues that are not actually issues, such as misclassified bugs or spam.
• large

  (1-2d) - This label is used for issues that can be completed within 2 days or less.
• medium

  (1d) - This label is used for issues that can be completed within 1 day or less.
• neve-38
• new feature

  Request for a new feature or functionality to be added to the project.
• on-hold

  Not being actively worked by being blocked or not having the capacity to work on it.
• php

  Pull requests that update php code
• pr-checklist-complete

  The Pull Request checklist is complete. (automatic label)
• pr-checklist-incomplete

  The Pull Request checklist is incomplete. (automatic label)
• pr-checklist-skip

  Allow this Pull Request to skip checklist.
• Priority-Critical

  Expected resolution time - up to 2 hours.
• Priority-High

  Expected resolution time - up to 2 business days.
• Priority-Low

  Expected resolution time - up to 3 months.
• Priority-Medium

  Expected resolution time - up to 1 month.
• product-marketing

  Issues reflecting product changes influenced by marketing strategy to foster market growth.
• product-milestone

  Important tasks for next product milestone. Prioritize these before others.
• QA
• question

  Can be used to identify issues that are asking a question about the code or how to use the project.
• regression

  Issue represents a change in behavior from a previous version that is not intended or desired..