Planning the Work - When the TodoList is too big - Kanban Project Management (Gitea) #128
Labels
No Label
/!\ On Priority - High Quality Tutorial
? Impossible Currently ?
Complex
Doable
Simple
To be improved / simplified / finished / fixed
pushed to prod (1 month external review)
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: nihilist/blog-contributions#128
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
as a continuation of #126:
in the case where you have a todolist that's 999x too big, you need to consider it as a project, which requires to be broken down into multiple todolists (or issues).
to help with that you can use gitea, where you create a project, and organize it following the Kanban workflow (backlog / todo / doing / done). Change it to your liking, for me i like the (to be assigned / assigned / to be reviewed / completed) workflow
Into which you create your tasks, and in it you list the todolist, for each task.
You also can label them for additional infos. I use labels to describe the complexity, and if it is supposed to be an improvement over an existing tutorial or not. Also a label mentionning which tutorial is going to yield good results
Work - Kanban Style Todolist (in gitea)to Preparing the Work - When the TodoList is too big - Gitea Kanban Project ManagementPreparing the Work - When the TodoList is too big - Gitea Kanban Project Managementto Planning the Work - When the TodoList is too big - Gitea Kanban Project ManagementPlanning the Work - When the TodoList is too big - Gitea Kanban Project Managementto Planning the Work - When the TodoList is too big - Kanban Project Management (Gitea)