How do you troubleshoot a Requirement stuck showing 'NOT COVERED' status in PractiTest?

1. Confirm whether any Tests are actually linked to the Requirement at all, since NOT COVERED specifically means zero linked tests
2. If tests should be linked but aren't showing, check whether the link was created on the correct Requirement, since a link can accidentally end up on a similarly named one
3. Verify you're looking at the right Requirement Coverage scope, since coverage can be scoped either to the last run of a linked test overall, or to runs within specific selected Test Sets
4. If using an integration with Jira or Azure DevOps, confirm the PractiTest panel inside that tool is reflecting the same linked tests, since a sync delay could show stale information
5. As a last step, manually re-link the intended tests to the Requirement and confirm the status updates immediately, since the calculation is automatic and shouldn't require a refresh

In almost every case, a persistent NOT COVERED status comes down to a genuinely missing link rather than a display bug, since the status calculation itself is a straightforward, automatic reflection of linked tests.