Correctly logging a Known Issue Bug from the Tracker

🎯 Purpose:
To ensure accurate bug reporting by linking to valid Known Issues from the tracker, especially when a test fails due to a previously reported bug.

✅ When to Use This:
When a test fails and the reason is already documented in the Known Issues (KI) list.

📍 Steps to Follow:

1. Go to the Tracker:
   • Access the tracker that holds the Known Issues list.
   • Look for the correct known issue related to the test failure.
2. Do NOT Use the KI ID Directly:
   • For example, PWT-170-KI-1 is NOT a valid bug ID.
   • The -KI-1 is only a label within the test cycle (like PWT-170), not the original bug ID.
3. Find the Original Bug ID:
   • Click to expand the known issue entry.
   • Look inside the summary or description area.
   • You’ll find the original bug ID in brackets like: [GAT-PWT-134-2].
   • That’s the correct and traceable bug ID (e.g., PWT-134-2).
4. Log the Bug on the Platform:
   • Go back to the test platform where the test failed.
   • Reach the tracker issue ID.
   • Do not paste the KI label (e.g., not “PWT-170-KI-1”).
   • Instead, enter the correct ID from the original cycle: PWT-134-2.

📝 Example:

• Current Test Cycle: PWT-170
• Known Issue Listed: PWT-170-KI-1
• Actual Bug ID Found After Expansion: PWT-134-2
• What to Log: PWT-134-2

🚫 Common Mistakes to Avoid:

• ❌ Logging “PWT-170-KI-1” as the bug ID
• ❌ Skipping expansion and using only what's visible in the list
• ❌ Assuming all KI bugs belong to the current cycle