Metadocumentation
open-collective
open-collective
  • Welcome
  • About
    • Introduction
    • Terminology
    • Company
    • Pricing
    • Community Guidelines
    • Values
    • Team
    • Investors
    • Contributing
  • Product
    • Features
    • Roadmap
    • Comparison
    • User Profile
    • Currencies
    • Log-in System
  • Collectives
    • FAQ
    • Creating a Collective
    • Quick Start Guide
    • Customize Collective
    • Change Core Contributors
    • Tiers & Goals
    • Add Fiscal Host
    • Change Fiscal Host
    • Transparent Budget
    • Expense Policy
    • Approving Expenses
    • Updates & Comms
    • Events
    • Funding Options
    • Data Export
    • Buttons & Banners
    • Integrations
    • Zero Collective Balance
    • Closing a Collective
  • Financial Contributors
    • FAQ
    • Payments
    • Website Badge
    • Organizations
      • FAQ
      • Bulk Transfers
      • Gift Cards
      • Sustainer Resources
    • Collectives
      • Collective to Collective donations
  • Expenses & Getting Paid
    • FAQ
    • Submitting Expenses
    • Expense Comments
    • Edit an Expense
    • Tax Information
  • Fiscal Hosts
    • FAQ
    • Becoming a Fiscal Host
    • Create a Fiscal Host
    • Fiscal Host Settings
    • Invoices
    • Payouts
    • Host Dashboard
    • Add Funds Manually
    • Refunds
    • Host Fees
    • Local Tax Support
    • Agreement Templates
    • Open Source Collective
  • Contributing
    • Design
      • Design Workflow
      • Design Contribution Guidelines
    • Development
      • Contribution Guide
      • Best Practice Guidelines
      • Bounties
      • API
        • Members
        • Users / Emails
        • Collectives
        • Events
      • README Integration
      • Architecture
      • Postgres Database
      • PayPal
      • Post-Donation Redirect
      • Custom Tweets
      • Manual Reporting
      • Github Permissions
      • Translations
      • Testing with Cypress
      • Collective's locations
    • Documentation
      • Style guide
      • Suggesting changes
    • Translation
  • Internal
    • Scope
    • Team Retreats
    • Brussels Summer Team Retreat
    • Host Admin Manual
    • Newsletter
    • Support
    • Issue Labels
    • DNS Troubleshooting
    • Developer Guidelines
    • Architecture
    • Testing
    • Queries
      • Gift Cards
      • Transactions
      • Ops
      • Collectives
      • Hosts
      • Analytics
      • Emails
    • Projects
      • Maintainerati Berlin 2019
      • Season of Docs 2019
    • The Open Collective Way
      • Values
      • Community Guidelines
      • Core Contributors Guidelines
      • Core Contributors: Communication
      • Core Contributors: Expenses
      • Core contributors: Leave
      • Core Contributors: Compensation
Powered by GitBook
On this page
  • Correct use of labels for issue triaging
  • Main Labels
  • Emergency
  • High Priority
  • Priority
  • Complexity Labels
  • Area
  • Extra Labels:
  • Bug Fix Friday (BFF)
  • Good first issue
  • Up for Grabs + Team
  • Up for Grabs
  1. Internal

Issue Labels

Correct use of labels for issue triaging

Main Labels

Bug Feature Enhancement

Emergency

These are issues that block critical flows for example Ledger issues such us (double charging, no charging, wrong charging, wrong assigning of subscriptions) Log in issues (user can't log in, user can't make a contribution) Expectation of resolving: immediately - On-call schedule applies

High Priority

These are issues that are impacting critical flows without blocking them or issues not on the critical flows that are widespread for example: Manage subscriptions (cancel, update) CSS issues in critical flows or system wide Expectation of resolving: when resuming work, before working on ongoing main projects

Priority

Issues that can wait for a week. Expectation of resolving: within the week. They don't take precedence over ongoing projects.

Complexity Labels

Understand the amount of energy and time it the issue needs. Simple: 2hs or less Medium: a day max Complex: +a day

Area

Backend Frontend Documentation Localisation Design Ledger Tiers Events Expenses Notifications Reporting

Extra Labels:

Bug Fix Friday (BFF)

Team label to classify what bugs we want to look at on Friday.

Good first issue

Good practice for someone new.

Up for Grabs + Team

Enhancements, improvements, issues that impact the team only To be grabbed by team-members when in between main projects or to do something different every now and then. Expectation of resolving: within a month.

Up for Grabs

Good contained issue for someone outside of the core team to take a stab at it.

PreviousSupportNextDNS Troubleshooting

Last updated 5 years ago