Assigned issues (2)
Resolution: These issues are already assigned to someone. Is the issue assigned to you? If there's nothing more urgent, try to finish what you started. Is the issue assigned to someone else? Are they actually working on it? Ask them if they are still engaged on the issue, and unassign it if they are not.
Average age: 26.0d, Avg wait: 0.0d
| ID | Au | Desc | As | Rea | Cr | Up | Re | Cmntrs | Labels | Tags |
| 26 |  |
Lacking linter |
| 3wk | 3wk |
type: code health
type: CI
priority: P2
|
assigned open-milestone
|
|||
| 27 | |
Lacking tests |
| 3wk | 3wk |
type: code health
type: CI
priority: P2
|
assigned open-milestone
|
Unassigned P0 issues: No matching items
Unassigned P1 issues: No matching items
Unassigned P2 issues (1)
Resolution: Fix bugs! This is the "fun" part. 1. Try to reproduce the issue. Some options for repro: • Use the demo's "custom content" tab • Write a new unit or integration test to simulate the scenario in the report • This lets you run tests in the lab on non-desktop browsers 2. If the issue cannot be reproduced, set "status: unable to reproduce" 3. Once the issue can be reproduced, try to fix it or assign it to someone who can
Average age: 997.8d, Avg wait: 0.0d
| ID | Au | Desc | As | Rea | Cr | Up | Re | Cmntrs | Labels | Tags |
| 28 | |
PRs should not be considered stale after a push | 2y | 4wk |
type: bug
priority: P2
|
open-milestone
|
Unassigned P3 issues: No matching items
Unassigned P4 issues: No matching items