Interpretation
The customer links directly to individual policy pages (e.g. /policies/:id) as part of a hardening controls reference doc. When someone follows one of those links, they land on the policy detail page, but have no way to see how many hosts are passing or failing that policy. To check results, they have to navigate back to the overview, find the right policy (potentially across multiple pages, since “Back to policies” returns to page 1 rather than the page the policy was on), and read the pass/fail columns there. The customer would prefer to see the pass and fail counts directly on the policy detail page, since it's just two numbers.
What's Fleet missing?
The individual policy detail page (/policies/:id) does not surface the policy's current pass/fail host counts. Fleet shows this data in the policies list view but does not expose it on the per-policy page. As a result, users who arrive at a policy via a direct link must context-switch to the overview to see results, and the “Back to policies” pagination behaviour makes that round-trip more disruptive than expected.
What does the customer's ideal workflow look like?
- Customer maintains direct links to each Fleet policy page.
- An IT admin follows a link and lands on
/policies/:id.
- The page displays the policy name, query, and the total number of hosts passing and the total number failing.
- The admin has the information they need and can act on it (e.g. investigate failing hosts) without returning to the policies overview.
A (terrible) example
Interpretation
The customer links directly to individual policy pages (e.g.
/policies/:id) as part of a hardening controls reference doc. When someone follows one of those links, they land on the policy detail page, but have no way to see how many hosts are passing or failing that policy. To check results, they have to navigate back to the overview, find the right policy (potentially across multiple pages, since “Back to policies” returns to page 1 rather than the page the policy was on), and read the pass/fail columns there. The customer would prefer to see the pass and fail counts directly on the policy detail page, since it's just two numbers.What's Fleet missing?
The individual policy detail page (
/policies/:id) does not surface the policy's current pass/fail host counts. Fleet shows this data in the policies list view but does not expose it on the per-policy page. As a result, users who arrive at a policy via a direct link must context-switch to the overview to see results, and the “Back to policies” pagination behaviour makes that round-trip more disruptive than expected.What does the customer's ideal workflow look like?
/policies/:id.A (terrible) example