fastruby / fastruby/points

Separate rejected stories from approved and pending

Abierto
#338 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Feature Request ux
Lenguaje dominante
Ruby
Estrellas
42
Forks
17
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**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:**

Production

**Describe the feature:**

This feature is similar to #316, but if I understood that issue right, it requests the ability to order by status, and my issue is to have rejected issues thrown to their own list to the bottom

> **As an engineer going through points stories for a roadmap**
> **I set a story status to "rejected"**
> **And I see it added to a rejected list towards the bottom, after approved and pending stories**

**Problem:**

The current problem is that, especially for projects with a lot of stories, those that were rejected pollute the list we need to go through and examine on wether the story applies or not. Having rejected stories gathered in their own list after the ones approved or awaiting examination would help with the annoying confusion of opening stories you have already looked at.

> **As a an Engineer>**
> **I want to have rejected stories apart from the other stories**
> **So that I can more easily track which stories I have researched or not**

**Mockups:**

![Image](https://github.com/user-attachments/assets/2442a29a-6943-443b-bb8f-a38d411c9de4)

**I will abide by the [code of conduct](https://github.com/fastruby/points/blob/main/CODE_OF_CONDUCT.md)**

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

Empieza por localizar la lista de historias y el comportamiento de ordenación por estado; después, compáralos con la discusión relacionada en el issue #316 y con el mockup proporcionado. Se considera terminado cuando las historias marcadas como rechazadas aparecen en su propia lista debajo de las historias aprobadas y pendientes, sin alterar la vista de roadmap existente.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
rails, ruby
Área
frontend
Tipo de issue
Nueva funcionalidad
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
38/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.