bcgov / bcgov/EPIC.track

Staleness - Issues

Open
#2,181 0 comments 0 reactions 0 assignees View on GitHub
Frontend Work technical feature V2
Dominant language
Python
Stars
5
Forks
19
Avg merge
1d 7h
Merged PRs (30d)
7

Description

---

Status staleness is 7/10+
Issue Staleness should be 14/20+

this might change in future, and one day we want Instance Admins to be able to modify that from a front end page

---

**As a** (type of user)

**I want** (goal)

**so that** (reason/ why/ value)

## **Acceptance Criteria**

### Scenario 1:

GIVEN ... (you or your condition)
WHEN ... (what you do)
THEN ... (what you see)

### Scenario 2:
xxxxxx

### Validation Rules?

(If yes, list here)

### Screenshot

(Link above will always be the most up-to-date version.)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. First clarify the intended staleness thresholds, the affected issue states, and the acceptance scenarios; then locate the existing staleness calculation and its tests. Done means the agreed thresholds are applied consistently, with validation covering the specified scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.