Ticket iterations

[gtaEPIC]

• Requires Ticket CRUD Operations #10 to be completed

Each iteration will be registered with the username, the date and time, and a comment.
It can be a status change or a ticket modification. This will provide detailed ticket
information as well as an audit trail.

An additional field should be added to Tickets. This field should basically be the audit trail for a ticket.
An iteration should:

• Be registered by a username
• Have a Date and time
• Have a comment
• Change the status or log the change of status
• Log if the ticket was modified (Could be tied into the Update operation)

[gtaEPIC]

The way I'm thinking is of two ways:

1. add a field to tickets that will be an array of objects. Each object is an iteration containing all the information of said iteration.
2. Make a new collection / model being a ticket iteration, and have a new field in ticket with an array that references an iteration

Though I think 1st option might be better