cachethq/core

Sticky Incidents

Closed

#64 opened on Oct 3, 2024

View on GitHubContributor guide
 (6 comments) (0 reactions) (1 assignee)PHP (82 forks)github user discovery
good first issuehacktoberfest

Repository metrics

Stars
 (227 stars)
PR merge metrics
 (Avg merge 10d 23h) (28 merged PRs in 30d)

Description

Incidents can be marked as “Sticky” which I think actually makes more sense to just be labelled as “Pin to top”. Logic needs implementing for this.

  1. Update language string from "Sticky" to "Pin to Top".
  2. Any "Sticky" incidents should be at the top of the timeline.

Contributor guide

Research direction
Examine the Incident model and timeline query to add a 'pinned' boolean attribute, then update the ordering logic to list pinned incidents first. Also update language strings from 'Sticky' to 'Pin to Top'.
Tech stack
php
Domain
backend
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.
Half day
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
GitPHP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60