docs(test-manager): Test Cases Trend automation split, table view, and Tester Assignment label

[sandeepyadav-lt]

Updates the Test Manager widgets page for three tickets now Ready For Deployment.

Ticket	Change	Doc impact
TE-28887	Test Cases Trend stacks by automation status	Section rewritten
TE-28963	Per-project Table view behind a View radio	Section rewritten + screenshot
TE-28434	Tester Assignment data fix	One clause

Why the Test Cases Trend section is rewritten, not extended

It described "a trend line of test cases created over the selected time period" in two bullets. The widget now stacks Automated vs Manual, offers three views, and draws a previous-period comparison line — so the existing text was inaccurate, not just incomplete. A reader following it would look for a line chart that no longer exists by default.

Now documented:

• Automated / Manual stacking.
• The View option — Stacked Bar (default), Stacked Area, Table — and what the per-project table contains and sorts on.
• The dashed previous-period line and that the legend carries the dates it covers.
• Drilldown from a bar, a point, or a table cell.
• That Interval re-buckets the trend.

Tester Assignment — one clause

TE-28434 was a data-correctness fix; the widget behaves as documented. The only user-visible difference is which field labels each bar, so the doc now says testers are identified by their Display Name. The rest of the section is untouched.

Screenshots

Two new .webp assets, following the page's existing require() convention with explicit dimensions:

File	Dimensions	Size
tms-test-cases-trend-stacked-bar.webp	899 × 315	20 KB
tms-test-cases-trend-table-view.webp	898 × 626	27 KB

Both are smaller than the page's existing analytics assets (44 KB / 48 KB). Relative paths verified to resolve from docs/.

Scope notes

• Only docs/analytics-modules-test-manager-widgets.md is touched. There is a second copy at static/docs/ with identical headings but roughly half the content; it looked like a stale or generated artefact, so it is deliberately left alone. Flagging in case it needs the same edit — happy to port it.
• "Click a bar, a point, or a table cell" assumes TE-29410 (drilldown from the Stacked Area view) ships in the same release. It is merged to main; if this page goes live ahead of that, the "point" case is not yet true for the area view.

🤖 Generated with Claude Code

[sandeepyadav-lt]

Applied a support-documentation review pass to this section (cc033f9d). Five fixes, all in the Test Cases Trend copy:

Fix	Why
Spelled out three-dot menu → Configure Widget → View	The View option had no path to it. The page's only stated navigation is the three-dot menu for filters, so a reader would open that, find filters, and stop. This audience is often not hands-on.
Documented the 50-project cap	The section said "per-project breakdown", which reads as all projects. An org with more would take a partial list for missing data. The widget itself states how many of the total are shown.
Stated when the comparison line is absent	It needs two complete intervals in the preceding period. A short range at a coarse interval draws no line and gave the reader no way to tell whether that was a bug.
Aligned on Automation Status	Now matches the page's own capitalisation and points at the classification Test Cases Summary already defines — that a case which is not Automated counts as Manual is not self-evident from the Trend section alone.
Removed a duplicated drilldown bullet	The page already has a drill-down tip covering all widgets; the new table-cell case is covered where the table is described.

Deliberately not asserted: the interval control is referred to in lower case rather than as an Interval label — the selector renders its current value and I have not confirmed the control's own label. Happy to capitalise it if someone can confirm.

Still worth a decision before merge: the View group only appears once the default_widgets display-option update has been applied to that environment. It is confirmed on stage but not yet on production. If this page goes live first, it documents a control that is not there yet.