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.

Sign up for GitHub

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

Jump to bottom

Extend POST /support/ (supportRequest model) with a new field: assetId #528

Open
zerwuff opened this issue Feb 2, 2024 · 2 comments · May be fixed by #534
Open

Extend POST /support/ (supportRequest model) with a new field: assetId #528

zerwuff opened this issue Feb 2, 2024 · 2 comments · May be fixed by #534
Assignees
@edwinvandenbelt
Labels
WT1 To be discussed at the next meeting
Milestone
1.6

Comments

@zerwuff
Copy link

zerwuff commented Feb 2, 2024 •
edited
Loading

Is your feature request related to a problem? Please describe.

Our customers need to send damage reports without any booking. To identify a broken bike, it is helpful to submit a bike number from the maas provider to the TO.
Therefore, we use POST support (supportRequest model)

Urgency

Minor
(we have a workaround - send the bike number in the comment field)

Additional context

Broken bike / damaged bike is found by the end user. This information needs to be sent to the TO for further processing.

Describe the solution you'd like

Extend the supportRequest model with a new field: licensePlate

Describe alternatives you've considered

Sent the bike number or license Identifier in the comment field, but this makes it hard to identify the correct bike (wrangle it out of the comment field which is pretty ugly)

Possible Implementation

supportRequest -> add new Field: licensePlate
@zerwuff zerwuff changed the title Extend POST /support/ to provide asset id Extend POST /support/ (supportRequest model) with a new field: assetId Feb 2, 2024
@edwinvandenbelt edwinvandenbelt added the WT1 To be discussed at the next meeting label Feb 5, 2024
@matt-wirtz
Copy link
Collaborator

matt-wirtz commented Feb 7, 2024 •
edited
Loading

Hi! How does it work in your context if there is no related booking?
Does the end user just type in some number that is printed on the asset/bike? How do you know which TO is responsible for this asset? Does the end user need to specify which brand/TO the asset belongs to?

@zerwuff
Copy link
Author

zerwuff commented Feb 8, 2024 •
edited
Loading

Hi, the user sees a bike on a station and types in the number printed on the bike and a short text ("brake broken").
There is no additional brand information required. With the bike number only, can identify the right asset on our ( the TO ) side.
When we receive such an event, we resolve the correct asset on our (TO) side and issue an operations ticket for that, so it can be fixed.
Identifying the right TO must me done from the MP side the same way like when creating a booking, i.e. the User has to choose it upfront from the MP's Application.

@edwinvandenbelt edwinvandenbelt added this to the 1.6 milestone Feb 14, 2024
@edwinvandenbelt edwinvandenbelt self-assigned this Feb 14, 2024
@edwinvandenbelt edwinvandenbelt linked a pull request Feb 14, 2024 that will close this issue
528 add asset id to support request #534
Open
@edwinvandenbelt edwinvandenbelt moved this to Done in WT1 Kanban Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@edwinvandenbelt edwinvandenbelt

Labels
WT1 To be discussed at the next meeting
Projects
WT1 Kanban
Status: Done
WT1 Kanban - old
Status: Done
Milestone
1.6
Development

Successfully merging a pull request may close this issue.

528 add asset id to support request TOMP-WG/TOMP-API
3 participants
@edwinvandenbelt @matt-wirtz @zerwuff