At Grey Software, we use Gitlab to manage our projects and code.
Planning and Tracking a project
Gitlab issues are used to collaborate on ideas, solve problems, and plan work.
This feature is used for many purposes and can easily be customized to the needs and workflow of the project.
How we process issues at Grey software?
At Grey Software we have developed a lifecycle for issues with the help of labels.
Each stage of the lifecycle has a specific label associated with it, which allows you to easily trace the issue's status.
This issue was created to track the task of designing and engineering the Product section of our landing website. !
This issue is an 'idea' to publish a new landing website
This issue is to 'brainstorm' the code flow for unlocking premium features for Github sponsors.
Every project has associated issues which can be viewed all at once to track the progress of the project.
Issues associated to Grey Docs.
The particular way we use weights at Grey software is by breaking apart an issue into tasks, writing out those tasks as markdown checklist items, and then once we have the final weight, we assign it to an issue.
Weights are not set in stone.
You can change the weight of an issue as you discover more about the solution, and it is also OK to assign weights retrospectively.
Issue boards allow us to plan, organize, and visualize a workflow for a feature or product release.
Issue boards help to visualize how issues are being processed, and are inspired by Kanban boards.
The following issue board exhibits:
* list of issues the team is working on.
* Team member to whom a particular issue is being assigned.
* Where the issues are in the workflow.
As the count of issues, merge requests, and epics grows in GitLab, it’s more and more challenging to keep track of those items. Especially as the organization grows with time. This is where labels come in. They help to organize and tag work so people can track and find the work items they are interested in.
Following is the list of some labels
Labels are a key part of issue boards. With labels epics, issues and merge requests can be easily categorized.
Comments and threads
GitLab encourages communication through comments, threads, and code suggestions which makes collaboration more easier.
Milestones are a way to track issues and merge requests created to achieve a broader goal in a certain period of time.
It can be seen in this milestone there are 6 issues and 5 merge requests and is 16% complete.
Further details are explained next
- Milestone Completion status
- Due Date : when the milestone due.
- Issue Details : no of open and closed issues.
- Merge Request Details : no of open and closed merge requests.
- List of on-going issue and merge requests.
- List of completed issues and merge requests
Iterations are useful for planning agile or agile-like sprints to capture action items to be completed within a specific time period.
Burndown charts show the number of issues over the course of a milestone.
Burnup charts show the assigned and completed work for a milestone.
When issues in a group share a theme across projects and milestones, you can manage them by using epics.
The possible relationships between epics and issues are:
- An epic can be the parent of one or more issues.
- An epic can be the parent of one or more child epics
One of the epics of Grey Software is mentioned below
- Epic title.
- Child epics or issues: two of the child issues are associated with this epic.
- Start date of the epic.
- Due date of the spic.
- Labels attached to it, we can know epic's status.
- Parent epics: the above epic has two parent epics.
Its Hierarchy is shown below.
What are some examples of epics in Grey Software
Epic boards tracks the existing epics through labels. They appear as cards in vertical lists, organized by their assigned labels.
Epics and milestones in a group containing a start date or due date can be visualized in a form of a timeline (that is, a Gantt chart). The Roadmap page shows the epics and milestones in a group, one of its subgroups, or a project in one of the groups.