[Tracking] Tasks page: place rows by status and priority, and derive parent status

未关闭
  • 哪里不对？
#388 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp
领域
backend-api-design

调研方向

This is a tracking issue for #384, #385, and #386; begin with #384, which defines how the Tasks page rows are placed by status and priority. Then review #385 for deriving parent status from subtasks; #386 is an API spike intended after the Tasks page behavior has seen real use. Done means completing the listed work in dependency order and respecting the cross-track dependency on #387.

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

描述

enhancement

Tracks the Tasks page work from the #382 spike: place each task by its own status and priority, with a parent as context for its open subtasks.

Order

  1. #384 — Place Tasks page rows by their own status and priority
  2. #385 — Derive a parent task's displayed status from its subtasks. Blocked by #384
  3. #386 — Spike: expose derived parent status through the API. Blocked by #385, and best done after the Tasks page version has had real use

Relationship to #366

#366 tracks the task update path and journal work. The two tracks can run side by side, with one dependency between them: #387 in #366 is blocked by #384, because the journal reuses the Tasks page's context-header rule. That also puts #384 ahead of #243 and #369.

主要语言
C#
星标
1
派生
0
平均合并
2 小时 2 分钟
30 天内合并 PR
98

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

nevridge/TaskFlow 的其他 Issue

查看 nevridge/TaskFlow 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

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