Label Style Guide
In order to improve organization and tracking of issues, the following labels should be used as described.
Section of Punchcard that this issue belongs to.
user managementcontent typesworkflowspermissionsinput pluginsrevisionsapiroutingdatabase
Issues that make Punchcard feel broken or prevent us from doing further work, but otherwise work as designed. High priority.
blockedblockerbugexternally blockedhotfix
Issues that affect a user's comprehension or overall enjoyment of Punchcard.
visual designmicrocopyuser experiencedeveloper experienceperformance
Environment that the issue is present in, either Punchcard core or its use as a module
coremodule
Issues that are necessary but less impactful for our users.
cleanuplegaltechnical debtexperience debttestsgreenkeeper
Issues that require further conversation to figure out how to proceed or what action steps are needed.
request for commentshelp wantedquestionresearchstrategystubprototype
Issues that will result in new functionality or releases.
feature
Issues that will iterate on existing functionality.
enhancementoptimization
Issues where action can be taken, but has not yet.
under considerationconsumable
Issues where no actions are needed or possible. The issue is either fixed or addressed better by other issues.
invalidwon't fixduplicateon hold
Epics track multiple stories together towards a desired outcome. Each epic should get a label unique to the core concept of the epic, usually 2-3 words. Epics should be labeled with their epic label and the epic label. Each story related to an epic should be labeled with that epic's label.
epic