Reporting a Bug

Reporting a bug in Projek ensures that system issues are properly documented, tracked, and resolved through a structured workflow. A well-documented bug report improves clarity, reduces back-and-forth communication, and speeds up resolution.

Accurate bug reporting requires detailed information about the issue, including how it occurred and what was expected to happen. Providing complete details helps developers reproduce and diagnose the problem efficiently.

Once submitted, the bug enters the tracking system, where it can be assigned, prioritized, and monitored until it is resolved and verified.

How to Report a Bug

Step 1: Access the Bugs Section

1. Navigate to Bugs from the main sidebar
   or

2. Open a specific project and select “Report Bug.”

   

Step 2: Enter Basic Bug Information

Provide the following details:

• Bug Title: A clear and concise summary of the issue.

• Bug Description: A detailed explanation of the problem.

• Project Association: Select the related project.

• Milestone (Optional): Link the bug to a specific milestone if applicable.

• Priority Level: Choose Low, Medium, High, or Critical.

• Severity Level: Select Minor, Major, Critical, or Blocker.

Clear classification helps teams determine urgency and impact.

Step 3: Document Technical Details

For accurate reproduction, include:

• Steps to Reproduce: List the exact actions that triggered the issue.

• Expected Behavior: Describe what should have happened.

• Actual Behavior: Explain what actually occurred.

• Environment Information: Include browser, device, operating system, or version details if relevant.

Providing complete information reduces delays in investigation.

Step 4: Assign the Bug (Optional)

You may assign the bug to:

• A developer

• A specific team member

• Leave it unassigned for triage

Assignment ensures accountability for resolution.

Step 5: Submit the Bug

Click “Report Bug.”

The bug will:

• Enter the first workflow stage (e.g., Open).

• Appear in Kanban, Grid, and List views.

• Be available for tracking and management.

Best Practices for Reporting Bugs

• Use clear and specific titles.

• Include screenshots or attachments when possible.

• Provide exact reproduction steps.

• Avoid vague descriptions.

• Set priority and severity accurately.

Detailed bug reporting accelerates issue resolution and ensures efficient quality management within Projek.