Course 3: Known Issues

Learn about Known Issues and how to work with them.

Known Issues

Known Issues (KI) management was developed to save time, improve bug relevance and provide faster turn-around time for test cycles.

This feature allows you to carry over issues that are known in the platform, into new test cycles. Known Issues can also be shared with testers so they don’t report duplicate bugs.

Known Issues Status
  • A blue “bookmark” tag is used to indicate Known Issues in the title column

  • A white or “unfilled bookmark” indicates an item that is no longer a known issue (but it was a known issue at the time of the particular test cycle you are viewing)

How Known Issues Work when Copying Test Cycles
  • Copying a test cycle that did not leverage Known Issues does not add any Known Issues to the new cycle and you will need to add them manually as we described previously

  • Copying a test cycle that had Known Issues in it does carry in those same Known Issues into the new cycle. In the Applause platform, this means those items are pre-selected in the Test Cycle Known Issues section, but you can still choose to de-select those and/or to select other Known Issues to be part of the new cycle

How to Add Known Issues to Test Cycles

Any issue that is approved in the platform will be automatically flagged as a Known Issue. If an issue is rejected, the dialog box will still give you the option of marking it as a Known Issue.

Steps to Assign Known Issues to a Test Cycle
  1. From the left-hand navigation, select “Test Cycles”.

  2. Click the Actions dropdown menu and select “Edit Test Cycle” for the cycle that you want to add Known Issues.

  3. Select Step 2 “Scope” and navigate to the “Testing Scope” then go to the “Known Issues” area and click the “Add Known Issues & BFV” button.

  4. Select the relevant previously reported Known Issues, to check the “Known Issues” box next to the relevant Known Issues.

  5. Click Done after you finish. Then remember to save the test cycle so your changes are implemented.

How to View the Added Known Issues

When reviewing test cycle results, Known Issues are separated in their own tab, so they are conveniently located, but not mixed in with new issues reported in this test cycle.

How to Remove Known Issues

You can manually “Unmark as Known Issue” anytime from the issues list or bug detail page.

Note: If a known issue is marked as “Won’t Fix”, then the bug remains as a known issue but can be unmarked manually.

Other Ways to Remove Known Issues
  • When a bug is marked as “Resolved”, the bug is automatically removed from the Known Issues list

  • When a bug passes the in-platform Bug Fix Verification (BFV) process, the bug is automatically removed from the Known Issues list