- @noahtalerman: Draft PR from hackathon in Boulder CO is here: https://github.com/fleetdm/fleet/pull/39764 ## Goal | User story | |:---------------------------------------------------------------------------| | As an IT admin, | I want to catch activities webhooks for new macOS, Windows, and Linux setup and macOS MDM migration | so that I can send messages in a Slack channel that helps me monitors how new Mac setup and MDM migration is going. ## Changes ### Product - [x] UI changes: Figma [wireframes](https://www.figma.com/design/5krysuQ5tk3YVhjYEU3jR2/Start-and-end-activities--macOS-setup-experience-and-MDM-migration?node-id=27-205&t=4EuY3a3nyR73Mrcv-1) - [x] CLI (fleetctl) usage changes: No changes - [x] YAML changes: No changes - [x] REST API changes: No changes - [x] Fleet's agent (fleetd) changes: No changes - [x] Fleet server configuration changes: No changes - [x] Exposed, public API endpoint changes: No changes - [x] fleetdm.com changes: No changes - [x] GitOps mode UI changes: No changes - [x] GitOps generation changes: No changes - [ ] Activity changes: [PR](https://github.com/fleetdm/fleet/pull/39728) - [x] Permissions changes: No changes - [x] Changes to paid features or tiers: macOS [setup experience](https://fleetdm.com/guides/setup-experience) and Fleet's [end user migration workflow](https://fleetdm.com/guides/mdm-migration#end-user-workflow) are Fleet Premium only. - [x] My device and fleetdm.com/better changes: No changes - [ ] First draft of test plan added - [x] Other reference documentation changes: No changes - [ ] Once shipped, requester has been notified - [ ] Once shipped, dogfooding issue has been filed ### Engineering - [ ] Test plan is finalized - [ ] Contributor API changes: TODO <!-- Specify changes in the the Contributor API doc page as a PR to reference docs release branch following the guidelines in the handbook here: https://fleetdm.com/handbook/product-design#drafting Put "No changes" if there are no changes necessary. --> - [ ] Feature guide changes: TODO <!-- Specify if a new feature guide is required at fleetdm.com/guides, or if a previous guide should be updated to reflect feature changes. --> - [ ] Database schema migrations: TODO <!-- Specify what changes to the database schema are required. (This will be used to change migration scripts accordingly.) Remove this checkbox if there are no changes necessary. --> - [ ] Load testing: TODO <!-- List any required scalability testing to be conducted. Remove this checkbox if there is no scalability testing required. --> > ℹ️ Please read this issue carefully and understand it. Pay [special attention](https://fleetdm.com/handbook/company/development-groups#developing-from-wireframes) to UI wireframes, especially "dev notes". ## QA ### Risk assessment - Requires load testing: TODO <!-- User story has performance implications that require load testing. Otherwise, remove this item. --> - Risk level: Low / High TODO <!-- Choose one. Consider: Does this change come with performance risks? Any risk of accidental log spew? Any particular regressions to watch out for? Any potential compatibility issues, even if it's not technically a breaking change? --> - Risk description: TODO <!-- If the risk level is high, explain why. If low, remove. --> ### Test plan <!-- Add detailed manual testing steps for all affected user roles. --> > Make sure to go through [the list](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/ui/design-qa-considerations.md) and consider all events that might be related to this story, so we catch edge cases earlier. 1. Step 1 2. Step 2 3. Step 3 <!-- Consider: Do the steps above apply to all global access roles, including admin, maintainer, observer, observer+, and GitOps? Do the steps above apply to all team-level access roles? If not, write the steps used to test each variation. --> ### Testing notes <!-- Any additional testing notes relevant to this story or tools required for testing. --> ### Confirmation <!-- The engineer responsible for implementing this user story completes the test plan before moving to the "Ready for QA" column. --> 1. [ ] Engineer: Added comment to user story confirming successful completion of test plan. 2. [ ] QA: Added comment to user story confirming successful completion of test plan.
Goal
Changes
Product
Engineering
QA
Risk assessment
Test plan
Testing notes
Confirmation