Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate rejected stories from approved and pending #338

Open
2 tasks done
mateusdeap opened this issue Jan 21, 2025 · 0 comments
Open
2 tasks done

Separate rejected stories from approved and pending #338

mateusdeap opened this issue Jan 21, 2025 · 0 comments

Comments

@mateusdeap
Copy link
Member

IMPORTANT: please make sure you ask yourself all intro questions and fill all sections of the template.

Before we start...:

  • I checked the documentation and didn't find this feature
  • 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

I will abide by the code of conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant