Ticketing System

[jon-nfc]

This epic is for the core design of the ticketing system. Although a majority of it is already developed. There is still a lot of work required to add the features that were part of the initial idea.

Details

Intent is to have a core ticket model, serializer and viewset that ALL tickets inherit from.

Models

• The currently implemented models will require a refactor.

The intent is that there will be a base ticket model, and all ticket type models will be sub-models. (inherit from core ticket)

• both ticket models, ticket and ticket comment will be made core ticket models with sub-tickets inheriting from them.

Migrations

There will be migrations tied to this change. as such the following will need to be adhered to so as limit the potential for data loss:

• The refactor of the models will require that there be new ticket models and not to use the same ones
• migration of data will need to be via a management command

Links

• Related: Location Management #62
• Related: Ticketing models #250
• Related: Release Management #462

Tasks

• New management command to move ticket data from old tables to new ones
• New Core Ticket Model
• New Change Ticket Model
• New Incident Ticket Model
• New Project Task Ticket Model
• New Problem Ticket Model
• New Request Ticket Model
• Add API field blocked as a status_icon
  intent will be to show on table view that the ticket is blocked by another ticket

Features

• Implement Validation for tickets that require approval