fleetdm / fleet

Open-source platform for IT, security, and infrastructure teams. (Linux, macOS, Chrome, Windows, cloud, data center)
https://fleetdm.com
Other
2.94k stars 409 forks source link

Upcoming activities: Add MDM commands #15920

Open noahtalerman opened 8 months ago

noahtalerman commented 8 months ago

Goal

User story
As an endpoint operator on the Host details page,
I want to see a list of the upcoming MDM commands and scripts
so that I know what upcoming commands/scripts will run on a specific host.

Changes

Product

Engineering

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

Context

QA

Risk assessment

Manual testing steps

  1. Validate MDM & DDM activity shows up in feed.
  2. Validate Script activity shows up in feed.
  3. Validate API activity
  4. Validate loading & error state in UI
  5. Test upcoming & past feeds
  6. Verify details modal match Figma
  7. Test created, deleted, ran, installed...
  8. Test macOS, Windows, and Linux

Testing notes

NOTE: New users will be displayed in the activity feed, mdm commands that were run prior to update will show "a user" Additional note: some of these tasks are already complete. e.g. Script and software installs

Confirmation

  1. [ ] Engineer (@____): Added comment to user story confirming successful completion of QA.
  2. [ ] QA (@____): Added comment to user story confirming successful completion of QA.
noahtalerman commented 7 months ago

@georgekarrv heads up, we moved this story to "Settled." I think we can start the spec'ing process while Rachael takes a look at API design.

@rachaelshaw when you get the chance, can you please take a look at the API design in Figma?

Please let us know if y'all have any feedback or questions.

marko-lisica commented 6 months ago

@roperzh Based on our discussion during design review today. This is behaviour we want:

cc @noahtalerman

georgekarrv commented 4 months ago

@noahtalerman For review

marko-lisica commented 4 months ago

Hey @georgekarrv I assigned myself to the story. I'll double-check if the designs are stale before we proceed.

noahtalerman commented 2 months ago

Hey @georgekarrv, heads up, I pulled the sub-tasks off drafting board (removed :product) to clean up the board. I think we can pull them back on when this story is ready for re-estimation.

cc @marko-lisica

georgekarrv commented 2 months ago

Listing out how this can be split

team said 3sp for UI for each and 5sp for backend each so napkin math 13*8 -> 104sp but we can slice and dice it to pick and choose which of these to prioritize.

noahtalerman commented 2 months ago

Hey @georgekarrv, @marko-lisica, and @Patagonia121 heads up, I pulled this story and #20301 (and sub-tasks) off the drafting board because it wasn't prioritized in the engineering sprint we just kicked off.

When we revisit this one, let's dig into the building one queue now v. unifying the queue later.

lukeheath commented 1 week ago

@georgekarrv I noticed the estimation on this and it seems very high. Each UI activity item is estimated at 3 points, but adding one activity item to the UI does not take an entire day (it takes me about one hour). In the VPP story, adding 5 UI activity items was estimated at a 3. Let's dig into these estimations before we bring into the next sprint; I may be missing something. Thanks!

noahtalerman commented 2 days ago

Hey @marko-lisica, heads up that I moved this story and "Fleet-initiated" story (#20712) into the drafting board.

When you get to this story, can you please bring Fleet-initiated designs into this story and close out the Fleet-initiated story (#20712) to simplify things for us? One story for adding MDM commands to the activity feed.

I think let's not worry about breaking up the story until we get to estimation.