octobox/octobox

Grey icon for "closed as not planned"

Open

#3,374 opened on Jun 29, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Ruby (311 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (3,737 stars)
PR merge metrics
 (Avg merge 9h 19m) (43 merged PRs in 30d)

Description

💥 Proposal

What feature you'd like to see

Github now distinguishes between successfully closed and "closed as not planned":

grafik

and uses different icons for that.

Both types are marked with the violet closed marker in octobox. It would be great if "closed as not planned" issues could get the grey icon in octobox as well.

Motivation / Pitch

Making the closed reason visible via the icon is a usability bonus. It helps to quickly judge the state of the issue. Additionally, using the violet closed icon in octobox for issues that have the grey icon in GitHub is somewhat confusing. When seeing the violet icon. I consider it as completed because that's the color semantics I've learned from GitHub.

Contributor guide

Research direction
Investigate how Octobox currently displays closed issue icons and identify where to add logic for 'closed as not planned' state.
Tech stack
rubyjavascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75