Separate rejected stories from approved and pending

未关闭
#338 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
rails, ruby
领域
frontend

调研方向

先定位 story 列表和按状态排序的行为,然后将其与 issue #316 中的相关讨论以及提供的 mockup 进行比较。当标记为已拒绝的 story 出现在已批准和待处理 story 下方的独立列表中,且不影响现有的 roadmap 视图时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

Feature Request ux

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

主要语言
Ruby
星标
42
派生
17
PR 合并指标
30 天内没有已合并 PR

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

fastruby/points 的其他 Issue

查看 fastruby/points 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。