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

Mute and unmute recommended services #35

Open
DanielCaspers opened this issue Dec 16, 2019 · 1 comment
Open

Mute and unmute recommended services #35

DanielCaspers opened this issue Dec 16, 2019 · 1 comment
Labels
Feature MyCar Edition The public facing info behind auth Needs API Needs REST API for further progress - work is blocked. Needs stakeholder action Needs action from one or more stakeholders

Comments

@DanielCaspers
Copy link
Owner

DanielCaspers commented Dec 16, 2019

Background
This feature was originally requested as a part of #25. It has been pushed out of original MyCar launch scope. The intent of postponement is to better understand the customer needs and use cases for the feature to determine how all actors are involved at which stages in these flows.

Muting a recommended service
Muting a recommended service is intended to have the client not have to see the last-marked state of a recommended service. This may be used when

  1. A customer has completed the work elsewhere since it has been noted
    1.1 Technicians should also be notified of this to pay extra attention to the work performed by other shops in case it was not performed properly.
  2. A customer has no intention of fixing the recommended service
  3. A customer wants a means of carefully selecting the recommended services to fix in a given visit if their budget restricts them from fixing everything.

Unmuting a recommended service
Should muting a recommended service be provided, the ability to undo this operation is desirable as

  1. The customer's budget or desire to fix the problem may change.
  2. The customer may accidentally mute a service.

Action items

  1. @scaspers and @YoMurphy must further define this feature and how it will interact with D3, service advisors, and customers before this can be scoped into a release. Decided not for first release of MyCar.
@DanielCaspers DanielCaspers added Feature MyCar Edition The public facing info behind auth labels Dec 16, 2019
@DanielCaspers DanielCaspers mentioned this issue Dec 16, 2019
6 tasks
@DanielCaspers DanielCaspers added Needs API Needs REST API for further progress - work is blocked. Needs stakeholder action Needs action from one or more stakeholders labels Dec 16, 2019
@scaspers
Copy link
Collaborator

scaspers commented Feb 5, 2020

We will put this feature off until a later date and gather more user input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature MyCar Edition The public facing info behind auth Needs API Needs REST API for further progress - work is blocked. Needs stakeholder action Needs action from one or more stakeholders
Projects
None yet
Development

No branches or pull requests

2 participants