Troubleshooting

Use this guide when UI behavior does not match expected policy/scope behavior.

1) Project badges disappear or do not persist

Checks:

• Confirm project metadata exists in storage after save.
• Confirm list rendering uses stored metadata, not temporary state.
• Confirm no post-render process clears environment/version fields.

Expected:

• Environment and version badges remain visible after refresh.

2) Existing projects relabeled to wrong environment

Checks:

• Confirm creation flow only writes metadata for the new project.
• Confirm no global migration runs automatically on project create.
• Confirm project list rows use per-project environment keys.

Expected:

• Existing project environment labels remain unchanged.

3) Scope set to inScope but control not added

Checks:

• Confirm rule targets correct component type.
• Confirm scope key spelling matches rule definition exactly.
• Confirm rule action adds the expected control ID.
• Confirm rule set for api is also applied to webApplication when intended.

Expected:

• Control appears immediately after matching scope condition.

4) Node border color appears incorrect

Checks:

• Confirm relevant scope fields are not notAssessed.
• Confirm color logic uses scope-specific assessment flags.
• Confirm unrelated unconfigured metadata does not force tertiary state.

Expected:

• Border color reflects actual scope assessment state.

Bug report template

Include:

• Environment type
• Component type
• Scope values before and after change
• Expected result
• Actual result
• Screenshot
• Repro steps