Denomas Project Management Hands-On Guide: Lab 5

This Hands-On Guide walks you through the lab exercises used in the Denomas Project Management course.

Denomas Project Management Hands-On Guide

LAB 5: ORGANIZE AND MANAGE ISSUES

A. Set issue metadata

In your Family Budget Calculator project, click Issues from the left pane.
Click your Third-party financial services integration issue.
In the issue’s metadata pane, click Edit next to the Epic field.
Assign this issue to the Investment Tracking epic.
In the issue’s metadata pane, click Edit next to the Iteration field.
Assign this issue to the first most recent iteration in Team sprints.
In the issue’s metadata pane, click Edit next to the Due date field.
Set the issue due date to 1 week from today’s date.
In the issue’s metadata pane, click Edit next to the Labels field.
Apply the label Status::WIP. Note this replaces the previous Status::Open label, since an issue can’t simultaneously have multiple labels with the same scope (the “Status::” part of the label).
In the issue’s metadata pane, click Edit next to the Weight field.
Enter a value of 2, then click away from the metadata pane to set the issue’s weight.
Navigate to DigiBit Technologies > Software group. In the left pane, click Epics. Click the Investment Tracking epic. Note that the Third-party financial services integration issue appears in the epic’s details page.
In the left pane, click Issues > Iterations. Click the iteration to which you assigned the issue. Note that the Third-party financial services integration issue appears on the iteration’s details page.

B. Organize, promote, and link issues and epics

In your Family Budget Calculator project, click Issues in the left pane.
Click your Back-end services issue.

You realize that, considering the scope of this initiative, this issue would be better suited as an epic, with each To-Do in the description as a separate issue in the epic.
To promote this issue to an epic, use the /promote quick action in the issue’s comment field, then click Comment.
Back-end services is now an epic at the Core group level. Using the breadcrumbs at the top of the page, click your Core subgroup.
In the left pane, click Epics.
Click into your new Back-end services epic.
You’d like to link the epic’s To-Do items as individual issues. Under the Child issues and epics tab, click Add > Add a new issue.
Enter Create DB as the issue title.
In the Project dropdown, select Family Budget Calculator, as it is the only project created so far, and all issues must belong to a project.
Click Create issue.
Use the same steps to to create issues titled Create service infrastructure and Back-end documentation, both linked to the Back-end services epic.
Click into the Create DB issue.
In the issue’s right metadata pane, assign the issue to the Back-End Services Deployed milestone.
Assign the Create service infrastructure and Back-end documentation issues to the Back-End Services Deployed milestone.

So far all issues have been created in the Family Budget Calculator project by necessity. But as requirements grow it may be best to move some issues into more suitable projects.
Navigate to your Software > Core subgroup.
From the Core group landing page, click New project, then Create blank project.
In the Project name field, enter Database
Leave the Visibility Level at the default selection.
Enable the Initialize repository with a README checkbox.
Click Create project.
Return to your Family Budget Calculator project in the Core subgroup.
In the left pane, click Issues.
Click into the Create DB issue.
On the issue’s details page, scroll to the bottom of the right metadata pane and click Move issue.
Select your Database project, then click Move.
See that the project heading and breadcrumbs at the top of the page indicate your issue is now part of the Database project.

C. Create and apply a description template

Navigate to your DigiBit Technologies group.
In the upper right corner of the group landing page, click New Project.
Click Create blank project.
Enter Description Templates as the project name. This project will hold templates that can be used to pre-populate issues and merge requests across the organization.
Enable the Initialize repository with a README checkbox.
Click Create project.
On the project landing page, click the (+) dropdown near the top of the page under the project title.
Click New file.
In the File name field, enter .gitlab/issue_templates/technical_spike.md

For the file’s content, paste the following:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15


## Instructions
Use this issue to capture research that must take place before continued development of a feature.

### Summary
<!--In 2 sentences or fewer, describe the problem to be solved or the question to be answered.  -->

### Impact Statement
<!-- Describe importance of solving the problem. How will it affect the feature or product direction?  -->

### Tasks
- [ ] Assign participants and DRI
- [ ] Apply appropriate priority and team labels
- [ ] Assign to an upcoming product sprint

/label ~"Status::Open"

Click Commit changes.
Using the breadcrumbs at the top of the page, navigate back to your DigiBit Technologies group.
In the left pane, click Settings > General.
Scroll to the Templates section and select Expand.
In the Select a template repository dropdown, select your Description Templates project.
Click Save changes.
Now the template can be applied when creating an issue. Navigate to your DigiBit Technologies > Software > Core > Database project.
In the left pane, click Issues.
Click New issue.
For the issue title, enter Identify tuning parameters to reduce performance bottlenecks
In the Description field, expand the Choose a template dropdown and select your technical_spike description template.
Optionally modify any details in the description.
Assign the issue to yourself and click Create issue.
Review the pre-populated description and metadata on the issue’s details page.

Suggestions?

If you’d like to suggest changes to the Denomas Project Management Hands-on Guide, please submit them via merge request.

Last modified November 29, 2023: big update (17188382)

View page source - Edit this page - please contribute.