Update docs on muting CSM issues

[janine-c]

What does this PR do? What is the motivation?

In this PR:

• I've updated the descriptions of where to find the mute button, which not only has moved, but now varies depending on whether the issue contains one or multiple resources
• I've removed the section about the Resource evaluation over time timeline, which has been removed from the UI

Merge instructions

Merge readiness:

• Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:

/merge

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/janine.chan/docs-9632-mute-findings-update/security/cloud_security_management/review_remediate/mute_issues

[neko-dd]

Small suggestions

[lucasdmaley]

Two things I noticed:

• If you select more than one resource in the table (in the aggregated resources view), the update is made using the setState dropdown

- Under **To view your organization's muted issues**, it's worth mentioning that the explorer is filtered by default to not show muted issues. To see muted issues in the explorer, the user should remove the @workflow.triage.status;(open OR in-progress) filter -> this can be done by hovering over it and clicking the X. - - I'd add this in before directing the user to click on "Muted" to sort the table, as that's the order they'd have to do it themselves

Overall, looks great - thanks again for catching and updating this!

[janine-c]

Thanks for flagging those, @lucasdmaley ! I've made those updates, so if you take another look at the preview page, you should see them there. Let me know how it looks and don't hesitate to let me know if you need any further changes :)

[lucasdmaley]

Thank you for making those changes @janine-c! Just noticed one thing -
Audit your muted issues doesn't describe the vulnerabilities explorer. Here, users can click on the "Muted" tab to see muted issues. Technically, the vulnerabilities explorer filters vulnerabilities by default with a slightly different filter - status:(Open OR "In progress") rather than @workflow.triage.status:(open OR in-progress), as in the misconfigs / identity risks explorers. Clicking on the "Muted" tab in the vuln explorer automatically removes this query though, so it might make sense to not make this slight discrepancy explicit in our docs :)

[janine-c]

Thanks, @lucasdmaley , great catch! I added the Vulnerabilities explorer - let me know if you think I got the nuance for that right, or if you'd like to work on the phrasing a bit more :) I appreciate your attention to detail here while I'm still learning the nuances of how these explorers work differently!

[lucasdmaley]

No worries at all! Phrasing looks right on what you added, I'd just make sure to add "Vulnerabilities" into this line:

By default, the Misconfigurations and Identity Risks issue explorers hide muted issues.

[janine-c]

@lucasdmaley Updated that wording - it originally omitted the Vulnerabilities explorer because it was leading into the part about manually removing those queries, but hopefully this is clearer :)

[lucasdmaley]

Ah, that makes sense - this is definitely clearer. Thank you for going back in to add all of these details, looks good to go!

[janine-c]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2024-12-10 19:38:19 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in master is 7m.