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

Self-service: Install Apple App Store apps on macOS #19620

Open
4 of 10 tasks
noahtalerman opened this issue Jun 10, 2024 · 15 comments
Open
4 of 10 tasks

Self-service: Install Apple App Store apps on macOS #19620

noahtalerman opened this issue Jun 10, 2024 · 15 comments
Assignees
Labels
customer-figali customer-junichi customer-rosner #g-mdm MDM product group :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Milestone

Comments

@noahtalerman
Copy link
Member

noahtalerman commented Jun 10, 2024

Goal

User story
As an IT admin on the Software page,
I want to add an Apple App Store app and make it available for my end users to install via Fleet Desktop
so that I can give end users (without an Apple ID) an easy way to install App Store apps that my organization ordered for them in Apple Business Manager.

Context

This is user story applies to this Fleet Q2 OKR:

  • Increase product maturity and fulfill customer promises

Changes

Product

Engineering

  • Update existing guide on VPP to include references to Self service.
  • 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

  • Risk level: Low

Manual testing steps

Note: the majority of the testing will be covered in ticket #18867

  1. In Fleet, add a VPP app to a team and ensure Self Service box is checked
  2. Verify the app shows up in Fleet Desktop on the assigned host device
  3. Verify app installs on host and behaves accordingly with all other Self Service expectations
  4. check that license counts are reflected accordingly after installs

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 noahtalerman added story A user story defining an entire feature :product Product Design department (shows up on 🦢 Drafting board) #g-mdm MDM product group customer-rosner labels Jun 10, 2024
@noahtalerman noahtalerman changed the title Self-service: Apple App Store apps on macOS Self-service: Install Apple App Store apps on macOS Jun 10, 2024
@noahtalerman
Copy link
Member Author

Hey @marko-lisica, I filed this separate "Self-service: Install Apple App Store apps on macOS" story here.

I think let's bring this through "Settled" and estimation separately from the "Install Apple App Store apps on macOS" story (#18867)

cc @georgekarrv

@georgekarrv georgekarrv added Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. and removed Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. labels Jun 19, 2024
@noahtalerman noahtalerman added ~feature fest Will be reviewed at next Feature Fest and removed :product Product Design department (shows up on 🦢 Drafting board) labels Jun 27, 2024
@noahtalerman
Copy link
Member Author

Hey @georgekarrv and @marko-lisica heads up, I pulled this story and the subtasks off the drafting board because it didn't make it into the engineering sprint.

I moved the story to feature fest so we can weigh it at the next feature fest.

@noahtalerman noahtalerman added :product Product Design department (shows up on 🦢 Drafting board) and removed ~feature fest Will be reviewed at next Feature Fest labels Jul 12, 2024
@georgekarrv georgekarrv added :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. and removed :product Product Design department (shows up on 🦢 Drafting board) labels Aug 5, 2024
@georgekarrv georgekarrv added this to the 4.56.0-tentative milestone Aug 8, 2024
@lukeheath
Copy link
Member

@georgekarrv Should this story be in ready for release? It looks like all of the sub-tasks are.

@georgekarrv
Copy link
Member

Switched it to Awaiting QA 👍

@lukeheath
Copy link
Member

@georgekarrv Thanks! Also I see some outstanding TODOs in the engineering checklist that need to be revised.

@PezHub
Copy link
Contributor

PezHub commented Aug 20, 2024

Found a bug and will revisit once fixed
#21423

@PezHub
Copy link
Contributor

PezHub commented Aug 22, 2024

created additional issues discovered while testing and will revisit once they are resolved.
#21496
#21497
#21498

@georgekarrv georgekarrv added :demo and removed :demo labels Aug 23, 2024
@PezHub
Copy link
Contributor

PezHub commented Aug 28, 2024

QA Notes:
Confirmed all of the above issues have been resolved. QA Approved!

@lukeheath lukeheath added :product Product Design department (shows up on 🦢 Drafting board) and removed :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. labels Sep 7, 2024
@noahtalerman
Copy link
Member Author

Hey @marko-lisica, can you please take this user story the rest of the way! It looks like there are two lingering checkboxes before we close it.

@zayhanlon and @Patagonia121 heads up that this customer request was shipped in Fleet 4.56. Leaving it open b/c updating the reference docs is still TODO.

@marko-lisica
Copy link
Member

Hey @noahtalerman I just resolved conflicts and created a new PR for API changes: #22102.

I'm not sure why "Permissions changes" is still unchecked. I assume this is implemented?

@noahtalerman
Copy link
Member Author

noahtalerman commented Sep 16, 2024

@marko-lisica thanks!

I'm not sure why "Permissions changes" is still unchecked. I assume this is implemented?

Do we need to update the permissions guide for this feature? Or, do we already have a line in the permissions table for adding software.

If we already have a line, can you please update the issue description to point to it? Thanks :)

I assigned you to the issue.

@noahtalerman
Copy link
Member Author

Hey @marko-lisica just followed up here w/ a ping!

When you get the chance, please check out my above comment here and help w/ next steps to get this story closed. Thanks!

@noahtalerman
Copy link
Member Author

Hey @marko-lisica just following up w/ another ping! as a reminder. Please let me know how/if I can help get this story closed :)

@marko-lisica
Copy link
Member

marko-lisica commented Sep 19, 2024

Do we need to update the permissions guide for this feature? Or, do we already have a line in the permissions table for adding software.

If we already have a line, can you please update the issue description to point to it? Thanks :)

@noahtalerman We already have "Add and delete software" row in permissions guide. I've just updated issue description.

Still need a confirmation on API design PR.

@noahtalerman
Copy link
Member Author

@marko-lisica thanks! Looks like @rachaelshaw followed up in your PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-figali customer-junichi customer-rosner #g-mdm MDM product group :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Development

No branches or pull requests

9 participants