Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose automatic install failures in UI if MDM is off or scripts are disabled. #25414

Closed
19 tasks
eugkuo opened this issue Jan 14, 2025 · 3 comments
Closed
19 tasks
Labels
~duplicate This issue or pull request already exists :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature

Comments

@eugkuo
Copy link
Contributor

eugkuo commented Jan 14, 2025

Goal

User story
As an admin,
I want to have better understanding of automatic software install failures if MDM is turned off or scripts are disabled
so that I can better troubleshoot the issue.

Key result

Original requests

We want to explain that automatic software installs will fail silently if MDM is turned off (App Store apps) or scripts are disabled (Fleet-maintained apps and packages).

After 4.63, I think the plan is to follow up to expose these failures in the UI. Eugene, can you please help us track a story for this? (edited)

Context

  • Product designer: _________________________

Changes

Product

  • UI changes: TODO
  • CLI (fleetctl) usage changes: TODO
  • YAML changes: TODO
  • REST API changes: TODO
  • Fleet's agent (fleetd) changes: TODO
  • Activity changes: TODO
  • Permissions changes: TODO
  • Changes to paid features or tiers: TODO
  • Transparency changes: TODO
  • First draft of test plan added
  • Other reference documentation changes: TODO
  • Once shipped, requester has been notified
  • Once shipped, dogfooding issue has been filed

Engineering

  • Test plan is finalized
  • 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

Test plan

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

Testing notes

Confirmation

  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.
@eugkuo eugkuo added story A user story defining an entire feature :product Product Design department (shows up on 🦢 Drafting board) labels Jan 14, 2025
@eugkuo
Copy link
Contributor Author

eugkuo commented Jan 14, 2025

@noahtalerman Here's the ticket wrt this slack message.

@noahtalerman
Copy link
Member

@eugkuo I think I asked you to filed a duplicate user story this: #25514

Sorry about that!

Closing this one.

@fleet-release
Copy link
Contributor

In the city of glass,
Errors shown, not hidden fast,
Admins breathe at last.

@noahtalerman noahtalerman added the ~duplicate This issue or pull request already exists label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~duplicate This issue or pull request already exists :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Projects
None yet
Development

No branches or pull requests

3 participants