Luke Heath

@noahtalerman This is ready for QA! To test effectively you'll need to be able to stand up a Fleet server locally. Is that something you can do? If not, maybe...

I am adding engineer comment that I have manually QA'd this user story.

@ilpianista Thank you for your contribution; this looks like a valuable addition. I am putting your pull request into our product drafting process so that our product team can confirm...

@jacobshandling @sharon-fdm I am leaving this on the Orchestration project board and assigned to milestone 4.70.0 because it technically shipped and was announced. Once this reaches "Ready for release" state,...

I don't know but maybe @sharon-fdm does?

@georgekarrv FYI looks like this doesn't have an estimate.

@noahtalerman I'm not sure if there is any immediate capacity, but this could be estimated and brought into the sprint as a [timebox item](https://fleetdm.com/handbook/company/product-groups#scrum-items).

@sgress454 Just a reminder that this is ready for re-review.

Converting this PR to draft until it is ready to merge to avoid impacting our weekly PR open time KPIs.

@noahtalerman @marko-lisica Why are we choosing to tie software patches to failing policies? That requires a distinct policy for every software item that would have to be maintained separately. Have...