Skip to content

No labels!

There aren’t any labels for this repository quite yet.

36 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
3rd-part-compatibilities
3rd-part-compatibilities
Issue or feature related to a compatibility with a 3rd party product.
accessibility
accessibility
Accessibility improvements or issues.
bug
bug
This label could be used to identify issues that are caused by a defect in the product.
3
customer report
customer report
Indicates the request came from a customer.
3
dependencies
dependencies
Pull requests that update a dependency file
1
doc-needed
doc-needed
This issue requires documentation updates or additions once it has been completed.
1
documentation
documentation
Improvements or additions to documentation
duplicate
duplicate
This issue or pull request already exists.
enhancement
enhancement
Request to improve or optimize an existing feature or functionality in the project
17
good first issue
good first issue
This could be used to identify issues that are suitable for people new to the project to work on.
1
help wanted
help wanted
This can be used to identify issues that the maintainers of the project would like some help with.
invalid
invalid
Could be used to identify issues that are not actually issues, such as misclassified bugs or spam.
javascript
javascript
Pull requests that update Javascript code
large
large
(1-2d) - This label is used for issues that can be completed within 2 days or less.
2
medium
medium
(1d) - This label is used for issues that can be completed within 1 day or less.
2
new feature
new feature
Request for a new feature or functionality to be added to the project.
2
on-hold
on-hold
Not being actively worked by being blocked or not having the capacity to work on it.
php
php
Pull requests that update Php code
1
pr-checklist-complete
pr-checklist-complete
The Pull Request checklist is complete. (automatic label)
1
pr-checklist-incomplete
pr-checklist-incomplete
The Pull Request checklist is incomplete. (automatic label)
pr-checklist-skip
pr-checklist-skip
Allow this Pull Request to skip checklist.
1
Priority-Critical
Priority-Critical
Expected resolution time - up to 2 hours.
Priority-High
Priority-High
Expected resolution time - up to 2 business days.
Priority-Low
Priority-Low
Expected resolution time - up to 3 months.
Priority-Medium
Priority-Medium
Expected resolution time - up to 1 month.
product-marketing
product-marketing
Issues reflecting product changes influenced by marketing strategy to foster market growth.
product-milestone
product-milestone
Important tasks for next product milestone. Prioritize these before others.
question
question
Can be used to identify issues that are asking a question about the code or how to use the project.
regression
regression
Issue represents a change in behavior from a previous version that is not intended or desired..
released
released
Indicate that an issue has been resolved and released in a particular version of the product.