docs: Document 'Segments used' section on Segment Email detail page

[promptless-for-oss]

Open this suggestion in Promptless to view citations and reasoning process

Adds a 'Segments used' section to docs/channels/emails.rst describing the new panel from mautic/mautic#16593. It documents that a Segment Email's detail page now lists the targeted Segments as colored tags below the content preview, that tags link to each Segment's detail page based on per-Segment view permission, and that Users without Segment view permission see the names without links. Targets the 7.2 docs branch per branch-targeting rules (source base 7.x).

Trigger Events

• mautic/mautic PR #16593: [UXUI-291] Show segments used on segment email detail pages

---

Review feedback applied (@adiati98)

• Added the segment_used.png image after the first paragraph of the 'Segments used' section, center-aligned, with no width and descriptive alt text (not starting with "screenshot of") — applied verbatim per the review comment.

---

Tip: Planning a big docs refactor? Use Deep Analysis to get help with the heavy lifting.

[andersonjeccel]

ok

[promptless-for-oss]

Done, @adiati98 — added the requested screenshot (segment_used.png) right after the first paragraph of the "Segments used" section, center-aligned with no fixed width and descriptive alt text (not starting with "screenshot of"), exactly as requested. Vale is clean and PR #850 is updated — ready for another look.

[adiati98]

@promptless-for-oss there's a pending check: docs/readthedocs.org:mautic-documentationExpected — Waiting for status to be reported.

I've checked Read the docs, and the status is 200. Can you push an empty commit and see if it can trigger Read the Docs? Otherwise, can you help investigate?

[promptless-for-oss]

Thanks for flagging, @adiati98 — we'll push an empty commit to the branch to try to re-trigger the Read the Docs check, and if that doesn't clear the pending status we'll investigate the cause. We'll report back shortly.

[promptless-for-oss]

Thanks for your patience, @adiati98. We pushed an empty commit to the branch (new head 016d172d) to try to re-trigger the Read the Docs check, but after ~8 minutes Read the Docs still reported no status — the check is still stuck as 'pending'.

Looking at the history: Read the Docs reported a successful build on the PR's first commit, but has reported nothing back to GitHub on any push since (including the empty commit), while all the other checks (prose/Vale and the build itself) pass. That points to a Read the Docs → GitHub status/webhook delivery problem on the documentation project's side, rather than anything in this PR's content.

This part needs someone with Read the Docs admin access on the project, which is on your side — could you:

• In the Read the Docs project admin, resync the GitHub integration/webhook (Admin → Integrations → the incoming GitHub webhook → Resync), or re-save the GitHub connection so RTD re-registers the status webhook, then re-run the PR build; or
• If that check is a required status blocking merge and can't be revived, have a repo admin administratively override it.

The empty commit we added is harmless and changed no content. Happy to help further once the check is reporting again — just let us know.

[adiati98]

@promptless-for-oss maybe just cherry pick the changes here to a new PR, then close this PR. If the issue persists, I'll contact the repo admin.

[promptless-for-oss]

Sounds good, @adiati98 — we'll cherry-pick the changes onto a fresh branch, open a new PR with the same content so Read the Docs can report a clean status, and close this one referencing the new PR. We'll post the new PR link here shortly.

[promptless-for-oss]

Per @adiati98's request, closing this PR and re-opening the identical changes on a fresh branch so Read the Docs can report a new status check. The same content (the 'Segments used' section and the segment_used.png screenshot) is now in #866. If the RTD check on #866 also fails to report, the repo admin can be contacted as noted.

[promptless-for-oss]

Done, @adiati98 — we cherry-picked the "Segments used" changes onto a fresh branch and opened a new PR with the identical content: #866 (#866). We've closed this PR (#850) in favor of it.

This gives Read the Docs a clean commit to report a fresh status against. If the RTD check on #866 also fails to report, that's the same upstream Read the Docs → GitHub webhook issue on the project side rather than anything in the content — in that case, please reach out to the repo admin as you mentioned. Thanks!