Implement ticket management

[vadrian89]

A ticket is what the dispatcher creates in order to match refugee needs with volunteers offerings.
The dispatcher should be able to manage all tickets created by him.

Required features:

• [x] create ticket;
• [x] view ticket;
• [x] view tickets list;
• [x] update ticket;
• [ ] ticket feedback

Optional features;

• [ ] automatic ticket feedback request;

About tickets: Tickets system is used by the group of volunteers to have a history on their activities this can help them to observe the flux of refugees and see how the needs increase or decrease. A ticket should contain the following data:

• number of adults
• number of children
• vehicle of transport used
• the destination (this can be an adress or volunteer's housing);
• status of the ticket (created/started/finished/canceled)
• feedback related to the ticket
• remarks;

The number of adults/children, destination (address) and remarks are text fields.

The vehicle of transport used should be a card when viewed which should contain the following info:

• registration number
• number of seats available When user taps the tile, it should pop-up a bottom sheet with aditional info about transport and user.

When editing or creating, it should be a tile which should show containe only the:

• number of seats
• destination
• icon of the type

Tapping on the tile, while creating or editing, should show a bottom sheet from which the user should search and find the transport needed, based on the completed fields.

The status of the ticket should be related to fields in the ticket document, meaning when you want to change the status you should set the field of that status.
The order of the statuses is the following:

1. created - de thefault state
2. started - when the volunteer(s) agreed and everything is in course
3. finished - when the dispatcher or volunteer closes the ticket using the feedback pop-up
4. canceled - when the dispatcher cancels the ticket

The dispatcher and higher privileged users can call the volunteer's number through a calling button. The volunteers can view the tickets which are related to them (either because of their transport or housing) The dispatcher can view the tickets which were created by him.

[vadrian89]

Because different type of volunteer offerings require different fields needed to split the tickets by type.

This means that every listing/pagination will be done by type and the counting for the collection to will be split by type also, in different documents.

[vadrian89]

Implemented ticket feedback by dispatcher, when cancelling/finishing ticket.