gitlab time estimation project management
step
- Create a Milestone in a Group
- Split tasks in Group/Repo, create Issues associated with Milestones, set Deadlines, and evaluate completion time
- Focus on task planning during development
Create a Milestone in a Group
Issue-milestone-new milestone-fill in milestone content-create milestone
View milestones
Use of Issue
- Issue in Group: development that is not specific to a certain part
- Issue in Repository: specific to the development of a certain part
- No matter which part of the Issue should be completed and closed
Two views of Issue: list view, kanban view (Group)
Create a new issue:
Time estimation/estimate time after creating the issue
After each commit, please comment/spend time in the Issue
Focus on task planning during development
- Before each development, you should create a development branch corresponding to an Issue to complete the corresponding Issue
- If there is an increase in the estimated time during the development process, it is necessary to update /estimate 2w 3d in the Issue in time
- For each commit part of the work, you should write this part of the work in the corresponding Issue
/spend 2w 3d - Every time you commit, you need to specify which Issue it is related to. git commit -m "This is my commit message. Ref #xxx"
is related to the Issue ID #The space before it cannot be lost
Complete and close Issue through MR
When a branch completes development and initiates a merge request, please note which Issue to close and who to notify by email
Through Closes (add space) and add # with Issue ID or Group Issue address, the corresponding Issue can be closed after MR is merged.
Similar to Issue, it needs to be assigned to the person responsible for merging (here we are the group leader) to associate with the milestone and mark it For type and priority,
please check the automatic deletion of related branches after merging.
If this MR is associated with multiple commits caused by many Fix problems, you should check the Squash option
