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

ZEVA: Separate Comment Boxes for Request and Reject on Vehicle Details Page #2373

Open
14 tasks done
Lalita-Lala opened this issue Dec 4, 2024 · 0 comments
Open
14 tasks done
Assignees
Labels
Medium Medium Priority Task Any work that does not directly impact the user

Comments

@Lalita-Lala
Copy link
Collaborator

Lalita-Lala commented Dec 4, 2024

Describe the task
Currently, the Vehicle Details page has only one comment box, which serves dual purposes:

  1. To provide additional details when making a request for more information about a vehicle (Request proof of range and range test results and/or a change to the range value from vehicle supplier, specify below.)
  2. To provide comments when rejecting a request.

This setup is confusing for users, as it is not intuitive that the same comment box should be used for two different activities with distinct purposes.

The task is to create two separate comment boxes on the Vehicle Details page: one dedicated to requests and the other to rejections. Each box will have its own functionality, layout, and tooltips to guide the user.

Additionally, when the Request checkbox is selected, a prepopulated comment currently appears in the comment field. This behavior needs to be removed, as the comment box should always be empty by default.

Prototype and mockups
mockups
proto

Purpose
Making the distinction between requests and rejections clear.
Reducing confusion by providing dedicated sections for each activity.
Ensuring users have clear instructions through tooltips on what actions are required to enable the buttons.

Acceptance Criteria
Request Section:

  • A titled box labeled Request.
  • Checkbox with the label: Request proof of range and range test results and/or a change to the range value from vehicle supplier, specify below.
  • A comment field is provided to add supporting details for the request (Add a comment to the vehicle supplier for request.)
  • No prepopulated comment appear after checkbox is selected
  • A disabled Request button that becomes enabled once: The checkbox is selected and a comment is added.
  • Tooltip behavior: When the button is disabled, the tooltip - “Select the checkbox and add a comment for the vehicle supplier to activate the request option.
  • Tooltip behavior: If the checkbox is already selected but no comment is added, the tooltip should prompt: Please add a comment for the vehicle supplier to activate the request option.

Reject Section:

  • A titled box labeled Reject .
  • Includes a comment field for the user to leave a rejection comment. (Add a comment to the vehicle supplier for reject.)
  • Tooltip behavior: When the reject button is disabled, the tooltip should prompt: “Please add a comment to the vehicle supplier to activate the rejection option."
  • Tooltip behavior: If the user has already selected the request checkbox, the tooltip should guide them to: "Please uncheck the request checkbox and add a comment to activate the rejection option."

Buttons (Request & Reject):

  • Both buttons are disabled by default
  • Request button: Becomes enabled when the checkbox is selected and a comment is added
  • Reject button: Becomes enabled only when a comment is added in the reject comment box and the request checkbox is not selected.
@ArawuSamuel1 ArawuSamuel1 added Task Any work that does not directly impact the user Medium Medium Priority labels Dec 4, 2024
@emi-hi emi-hi self-assigned this Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Medium Medium Priority Task Any work that does not directly impact the user
Projects
None yet
Development

No branches or pull requests

3 participants