CodeBlanks Logo Icon CodeBlanks

Summary - Issues

Combine the issue flow to manage a bug report.

Summary - Issues

When managing a bug report, first create an issue with a clear title and detailed description. Then categorize it with suitable labels such as bug. You can use the issue to track the problem and its resolution.

Create an issue
Add a title and description
Assign labels
Track progress

Practice Complete the Bug Report Details

Define the title, description, and label for a bug report. The title must be Profile page error, the description Profile data is missing, and the label bug. Print the values on separate lines.

Starter code

terminal
# Hata bildirimi alanları
issue_title = None
issue_description = None
issue_label = None

Sample solution

terminal
issue_title = "Profile page error"
issue_description = "Profile data is missing"
issue_label = "bug"
print(issue_title)
print(issue_description)
print(issue_label)

Expected output

Profile page error
Profile data is missing
bug

Questions and answers

Review the lesson questions together with their answers. To test yourself, solve the lesson interactively.

1 Which label can distinguish a bug report from other tasks?

  • origin
  • enhancement
  • bug Correct answer
  • upstream

Explanation: The bug label identifies the record as a bug report and makes issue classification easier.

2 Complete the Description Field

Question
Bir issue kaydının ayrıntılı açıklaması ____ alanında yazılır.
Answer
Bir issue kaydının ayrıntılı açıklaması Description alanında yazılır.

Explanation: The Description field contains the details of the problem or request.

3 Bug Report Workflow

Term Meaning
Issue A record for tracking a bug or task
Title Describes the problem briefly
Description Explains how the problem occurs
Labels Categorizes the record by type

All lessons in Intermediate

20 Intermediate final

  1. Branch management
  2. Rebase
  3. Conflict
  4. PR flow