aws-samples / aws-samples/sample-long-running-app-harness
[FEATURE] Prioritization of Issues
Open
agent-complete
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
### Feature Name
Prioritization of Issues
### Feature Specification
Prioritization of Issues
Would like to see if an issue is important or not. Would like an alert if they are critical issues.
### Acceptance Criteria
_No response_
### Estimated Complexity
Small (< 1 hour)
Contributor guide
Research direction
The issue names no files, tests, or entry points. First clarify how issue importance and critical alerts should be determined, who receives them, and what the acceptance criteria are; the work is done when those behaviors are defined and testable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100