Labels

Feature requests in disguise, intentional project choices, or user inexperience (PEBCAK). Instead of closing, consider 'document' flow label, as this might be a symptom of lacking docs.

Issues outside the scope of the project, it isn't our problem. If needed, ensure reporter is made aware of where to go instead.

Library AND Framework AND Platform domain

Framework AND Platform domain, NOT Library.

aka: server-side, backend. Databases, APIs etc..

Library AND Framework domain specific

aka: client-side, frontend, browser. Likely Javascript/HTML.

Platform specific

Making things look and feel nice (✿◡‿◡)

Specific to Community Edition. Issues covering all editions DON'T require an Edition label.

Exclusive to Pro Edition

Important to big business. DOESN'T imply priority!

aka: Ideation / Open for input. Ideas can forgo 'when' label. Initial flow stage.

A champion is needed to take this issue on, do you have what it takes? 💪

Someone's working on it! Is it you? Ensure you assign yourself, or ping a team member in the comments so they may do so for you.

Someone has taken ownership but has not begun work yet. Check time in this state to ensure issue health.

Being worked on, but requires a second (or nᵗʰ) opinion

Let's try to break it. Does it provide results matching original intent?

Documentation needed. When used in tandem with 'Not bug' ensure related/duplicate issues are located and reviewed for additional insight.

Ready for release! Add to release notes (ref. issue #) and close ticket! 🥂