Issues that describe an unexpected behaviour in an existing functionality.
"bug" or "support" issues that have a fatal impact on the customer's system (i.e. crash).
Pull requests that update a dependency file
Used by the "DEP" app to mark PRs and issues that depend on other PRs or issues.
Issues that require a change or addition in the respective documentation, once implemented.
Pull requests that must not be merged yet, e.g. because another pull request must be merged first.
Issues that describe new features or improvements to existing features.
Feature issues which are so large they need to be broken down before implementation.
Issues that require informing customers once solved or released (not in combination with "support").
"bug" issues that completely break a business process, with no reasonable workaround available.
"bug" issues that are neither "critical" nor "major".
Issues that require manual testing by a member of @pickware/sales before release.
Issues that were created to ask for clarification on how something works or is supposed to work.
Issues that describe one or more code changes that neither fix a bug nor change the business logic.
Issues/PRs pertain to rewrite and should not go into the normal backlog lane for the product.
Issues that directly correspond to a support inquiry and requires a code-level analysis.
Independent non-functional tasks or subtasks of user stories and bugs.
Issues for the Shopware 5 product line which we won't implement / fix anymore.