Order stories by status
- Dominant language
- Ruby
- Stars
- 42
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
**IMPORTANT: please make sure you ask yourself all intro questions and fill all sections of the template.**
**Before we start...:**
- [X ] I checked the documentation and didn't find this feature
- [ X] I checked to make sure that this feature has not already been requested
**Branch/Commit:**
Inform what branch/commit/version of "Points" you are using.
**Describe the feature:**
Please include a detailed description of the feature you are requesting and any detail on it’s expected behavior.
> **As a \**
> **I do \**
> **And then I do \**
> **And I see \**
**Problem:**
Currently, points are not ordered by status. It would be a nice feature after updating the status of the points story, stories with a status of rejected are moved to the bottom of the list.
> **As a \**
> **I want to \**
> **So that I can achieve a \**
**Mockups:**
Include any mockup idea related to the requested feature if it applies.
**Resources:**
If you have resources related to the implementation or research for this feature, add them here.
**I will abide by the [code of conduct](https://github.com/fastruby/points/blob/main/CODE_OF_CONDUCT.md)**
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, branch, or commit is named. Start by locating the points story list and the status-handling entry point in the Rails application, then determine how ordering is currently applied. Done means stories with rejected status appear at the bottom after a status update, with the intended ordering of other statuses confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100