Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Highlight severity of a bug in bug lists

Open
#116 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Start by reviewing pull request 114 and the linked review for the intended severity behavior. Then locate the bug-list rendering entry point and verify that blocker, critical, and major bugs are visibly marked while other severities remain unaffected.

Written by the indexing model from the issue text.

Description

Lets mark a bug with its severity if its a blocker, critical or major.

See https://github.com/k88hudson/bugzy/pull/114#pullrequestreview-230809461

Dominant language
JavaScript
Stars
11
Forks
14
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/bugzy

All issues in mozilla/bugzy

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.