UI to add software to many teams

[rachaelshaw]

Goal

User story
As help desk at a white label MSP,
I want to upload a Windows package to many teams
so that I can trigger a software install using the Install package API.

Context

• Requestor(s): @ddribeiro
• Product designer: @rachaelshaw

Changes

Product

• Reference documentation changes: N/A
• UI changes: Figma (MSP dashboard)
• CLI (fleetctl) usage changes: N/A
• YAML changes: N/A
• REST API changes: N/A
• Fleet's agent (fleetd) changes: N/A
• Permissions changes: N/A
• Changes to paid features or tiers: Fleet Premium
• Once shipped, requester has been notified

Engineering

• Feature guide changes: TODO
• Database schema migrations: TODO
• Load testing: TODO

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

QA

Risk assessment

• Requires load testing: TODO
• Risk level: Low / High TODO
• Risk description: TODO

Manual testing steps

1. Step 1
2. Step 2
3. Step 3

Testing notes

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]

Hey @zayhanlon, heads up this didn't make the 3 week drafting timeline. We left it on the drafting board b/c the plan is to carry this into the upcoming design sprint.

[rachaelshaw]

Estimate:
5 if we don't store the installers/just add them to teams' packages available for install
2 more for storing the installers & allowing for not assigning them to a team

[noahtalerman]

Hey @eashaw, chatting w/ @rachaelshaw about how we're going to store packages that aren't assigned to any team in Fleet.

Please chat w/ @mikermcneil about options for this. I remember Mike saying that we could avoid adding config (ex. S3) by storing packages in the database.