Skip to content

No labels!

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

280 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
team: Flux
team: Flux
8
team: Fuel
team: Fuel
WC Marketplace transactions and subscriptions
6
team: Ghidorah
team: Ghidorah
WC Onboarding
95
team: Kirigami & Origami
team: Kirigami & Origami
WC Store Editing (FSE)
1,180
team: Moltres
team: Moltres
Transact merchant experience. WooPayments, merchant onboarding
16
team: Mothra
team: Mothra
WC Merchants activation and store management
1
team: Proton
team: Proton
WC Core development and maintenance
702
team: Rubik
team: Rubik
Store API checkout endpoints, Mini-Cart, Cart and Checkout related issues
520
team: Singularity
team: Singularity
9
team: Solaris
team: Solaris
WC Release and Release Quality
40
team: SomewhereWarm
team: SomewhereWarm
A number of WC extensions
6
team: TBD
team: TBD
Issues in areas where there is no team doing active development.
92
team: Transact
team: Transact
WooCommerce Payments, WooCommerce Subscriptions and WooCommerce Stripe
52
team: Ventures
team: Ventures
WC Marketing including Facebook, Pinterest, Points & Rewards
11
team: Vortex
team: Vortex
WooCommerce monorepo tools and test suite.
224
test type: blocks-e2e
test type: blocks-e2e
20
test type: core-e2e
test type: core-e2e
10
tool: monorepo infrastructure
tool: monorepo infrastructure
2
tools
tools
5
type: bug
type: bug
The issue is a confirmed bug.
837
type: community contribution
type: community contribution
812
type: compatibility
type: compatibility
36
type: cooldown
type: cooldown
Things that are queued for a cooldown period (assists with planning).
71
type: dependencies
type: dependencies
Pull requests that update a dependency file (used by renovate).
2
type: duplicate
type: duplicate
The issue/PR is a duplicate of another issue.
type: enhancement
type: enhancement
The issue is a request for an enhancement.
1,036
type: epic
type: epic
Container issue with high-level description of work that will be done in sprint.
61
type: fatal
type: fatal
Reports of fatal errors
16
type: good first issue
type: good first issue
The issue is a good candidate for the first community contribution/for a newcomer to the team.
135
type: has use case
type: has use case
For any issues or PRs that include a use case description for a feature.