Warning: Unspending time can make a mess of time logs
It can be hard to track where/when you've spent and unspent time when working across several issues. Try to avoid this at all costs.
| Scrum Term | Gitlab Term |
|---|---|
| Sprint | Milestone |
| PBI | Issue |
| Story Points | Weight |
| Pull Request (PR) | Merge Request (MR) |
| Subtask | Task |
| Jira Functionality | Issues |
| Confluence | Wiki |
| Bitbucket Functionality | Repository |
Here, you will put your beginning and end dates in addition to your Sprint Goal. Note that Milestones CANNOT OVERLAP IN DATES so you must end a milestone the day before you begin a new one.
You must create Milestones at the group level, rather than Milestones that are attached to a specific repo. Group level Milestones work across separate repositories, which is useful if you've divided your code into frontend and backend repositories.
For each issue you create in your SPRINT backlog, be sure to add weight, the ToDo label, and select the milestone to associate the issue with.
In the description of an issue, - [ ] translates to a checkbox, which will show up on the list of issues adjacent to the issue title.
In a comment on the issue you're estimating, write /estimate 8h
You can also remove estimates by typing /remove_estimate
Format: message describing your contributions /spend 1h 2019-03-17
Note that you must put the /spend command on it's own line after the entire rest of the message.
You can subtract time by spending negative hours i.e. /spend -1h 2019-03-17
Message: should link to commits, issues, merge requests, and branches as you see fit. You can link to those in the Gitlab comment easily by following this format.
| Commit | Pasting the entire commit number from the branch or MR will automatically create a link |
|---|---|
| Issue | #X where X is the number of the issue |
| Merge Request (MR) | !X where X is the number of the MR |
| Label | ~X where X is the name of the label |
From your issue in Gitlab, you may click "Create Merge Request" which will create a branch and corresponding MR in one step. This will automatically connect the issue and MR by placing "Closes #X" in the description of the MR, so the merged MR closes the corresponding issue.
i.e. ToDo, In Progress, Needs Review, Done/Merged, Blocked
Visiting the Issue Board for the first time will create your ToDo and Doing columns for you
We recommend creating labels to arrange the priority of your tasks. You can create a label as described above.
Example: High Priority, Medium Priority, Low Priority
You can the view those labels in your Product Backlog or Issue Board, and you can sort by them (Label Priority)
This is located under the details for the current Milestone