GitLab with Git Fundamentals - Hands-On Lab: Create a project and issue

Estimated time to complete: 30 minutes

Objectives

A GitLab Project is a repository where you can store your code, as well as supplemental files such as configuration files. You can also use projects to track issues, plan work, collaborate on code, and continuously build, test, and use built-in CI/CD to deploy your app. You can find out more information about GitLab projects in the documentation

GitLab provides various tools for tracking and managing projects. In this lab, you will learn how to create a project, create an issue, create labels at a project level, and apply quick actions to an issue.

Task A. Access your Training Group

1. Navigate to https://gitlabdemo.com/invite in a web browser.

2. In the Invitation Code field, enter the invitation code provided by your instructor or in the LevelUp LMS.

3. Select Provision Training Environment.

4. On the confirmation page, locate the Your GitLab Credentials section. Read this section carefully, noting the credential information provided and the expiration date. Your access to this group and all of the projects that you create is ephemeral and will be deleted after the expiration date.

5. Click the Download Credentials button to download your temporary GitLab credentials.

6. Click on My Group.

7. Login with your temporary GitLab Credentials.

   This group your temporary account has been created in has a GitLab Ultimate license to see all of the features available.

8. Click on the ‘Create a project tile.

   From this point forward, both the self-paced training and the instructor-led training can follow the same instructions.

Task B. Create a project

1. Select the Create blank project tile.

2. In the Project name field, enter Top Level Project.

   The project slug will automatically populate. You can change this to a shorter string if desired for your own project. Leave it at the default for this lab.

3. In the Project URL field, click the dropdown for the second half of the URL to make sure it’s pointing to a group name and not a username. You should create this project inside a group, not directly in your user’s namespace.

4. Under Visibility Level, ensure Private is selected.

   Since the parent group above your group is private, all child groups and projects below will be private. You can learn more about project visibility levels in the documentation.

5. Check Initialize repository with a README.

6. Select Create project.

Task C. Create an issue

Issues are a core building block in GitLab that enable collaboration, discussions, planning and tracking of work. Issues belong to Project and not a Group. When viewing issues at the group-level, you can see all of the issues that have been created across all of the projects in that group. You can read more about them here.

1. In the left-hand navigation pane, navigate to Plan > Issues.

2. Click the New issue button.

3. In the Title field, type in My first issue

4. In the Type dropdown, make sure that Issue is selected.

5. The description is an optional section, but feel free to type in your own description for this issue.

   In the description section, there is a dropdown to select a template. It is possible to create templates to help standardize issue descriptions. To learn more about issue templates, click here.

6. Using the Assignees dropdown, assign the issue to yourself by clicking on the dropdown, and then clicking on your username.

   Alternatively, you can also click Assign to me directly beside the Assignees dropdown to assign an issue to yourself.

7. While we will leave the options as they are for now, it is important to understand what they do:

   • Epic: Associates the issue with an epic. An epic is a parent grouping of one or more child issues. You can think of an epic as a initiative or meta-level topic and an issue as an objective or detailed task for that initiative.

   • Milestone: Milestones in GitLab are a way to track issues and merge requests created to achieve a broader goal in a certain period of time, usually associated with a release and/or version number.

   • Labels: Apply labels to your issue, which are metadata tags that can be used to sort and filter your issues.

   • Weight: Apply a weight value to your issue to measure the time, complexity, or value a given issue has or costs.

   • Due date: Use in issues to keep track of deadlines and make sure features are shipped on time. You will receive an email reminder when an issue due date is approaching if it has not been closed yet.

   • Iteration: Associate the issue with an iteration to track it over a period of time. This allows teams to track velocity and volatility metrics.

8. Click the Create issue button.

Task D. Create custom labels

Labels allow you to organize and tag your work. Using labels will make it easier for you to track issues you are interested in using features like dynamic filtering. Some examples of using labels include: categorizing epics, issues, and merge requests using colors and descriptive titles like bug, feature request, or docs. You can read more about labels in the documentation.

1. In the left-hand navigation pane, navigate to Manage > Labels.

2. Click the New label button.

3. In the Title field, type Opened.

4. The Description field is an optional field used to describe a label. Feel free to enter anything in this field, or leave it blank.

5. Select any background color.

6. Click the Create label button.

   When you create a label in a project, the label is created at the project level. This means that the label will not be available in any other projects. It is possible to also create a group level label, which is available to all projects in a group.

7. Using the previous three steps, create two additional labels with the titles Completed and Needs documentation. These labels can have any background colors that you desire.

8. You now have 3 labels that are now available for you to assign to any issue, merge request, or epic in your project.

Task E. Assign labels to an issue

1. Navigate to Plan > Issues.

2. Click on the title of My first issue to open the issue.

3. In the right sidebar of My first issue, click Labels > Edit.

4. Click the Opened and Needs documentation labels you created earlier.

5. Click away from the Labels section. Notice that the issue now has both labels applied.

   The labels won’t apply to the issue until you click away from the labels section to close the multiselect box.

Task F. Use a quick action

A quick action is a text-based shortcut for common actions that are usually done by selecting buttons or dropdowns in the GitLab user interface. You can enter these commands in the description or comment for issues, epics, merge requests, and commits.

For more information about quick actions and to see a full list of possible quick actions, see the documentation.

1. In the comment field for the issue from the previous task, type the quick action /spend 1 hour

2. Click the Comment button.

   Notice that in the right-hand information pane, Time tracking now shows Spent: 1h. Instead of leaving a text comment, the quick action has updated the time spent working on the issue.

Lab Guide Complete

You have completed this lab exercise. You can view the other lab guides for this course.

Suggestions?

If you’d like to suggest changes to the lab, please submit them via merge request.

View page source - Edit this page - please contribute.