[Feature request] Project-controlling through collections and Roadmap

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
backend, frontend

调研方向

This is a multi-part feature request covering roadmap collapse/expand, an iterations toggle, user indicators on roadmap items, and a row height offset fix. Start from the roadmap view in the Svelte frontend and the Go handlers that serve roadmap data, but the payload does not name specific files. Done would need the maintainers to agree on scope, since it bundles several separate changes.

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

描述

fixed-0.9.3

In our constellation we differentiate between two workspace types: client-space and product-space.

client-space has several epics with the work item type client-project and start and end dates. Those cluster the todos for this "project phase".

product-space has a few epics with the work item type internal-project with start and end dates. For the product-space we often use iterations to cluster items instead of creating an interal-project epic (depends on the scope and context of the project).

In theory we wanted to visualize what projects (internal and client) are currently overlapping to establish an overview that can be filtered by person - or used for planning (extending project phases, shortening them, delaying them etc, distributing sub-tasks throughout the epic phase)

To fully utilize this idea we need the option to:
  • collapse/expand all tasks feature like in the tree-view for roadmaps.
  • adding a toggle to enable iterations in the overview
    • Without the iterations in the roadmap we would need to create a dummy task for the iteration and script some automatic function that syncs the iteration items as child items of this card along with the dates
  • adding a user indicator to the roadmap item; referencing issue #285
  • fixing the height offset of item to timeline row
Image
主要语言
Go
星标
421
派生
50
平均合并
17 小时 34 分钟
30 天内合并 PR
80

环境准备

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

从这里开始

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

Windshiftapp/core 的其他 Issue

查看 Windshiftapp/core 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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