Update the database migration to allow for new optional fields in ticket table

[humansinstitute]

Ticket Name: Update Database Migration for Optional Fields in Ticket Table

Context

• This ticket aims to address the need for additional optional fields in the Tickets table to enhance data granularity and provide more comprehensive records.
• The new fields will allow for better categorization (ticket_group) and attribution (author, author_id) of tickets, which will improve reporting and tracking capabilities.
• These changes are part of a broader initiative to upgrade the ticket management system by improving data structure and performance.

Task

1. Create a new database migration script to add the following optional fields to the Tickets table:
   • ticket_group (VARCHAR)
   • author (VARCHAR) // NOTE AUTHOR will be either Agent or Human
   • author_id (VARCHAR). // NOTE AgentID will be driven by - or HumanID would be
2. Add appropriate indexes to the new fields to maintain query performance:
   • Index on ticket_group
   • Index on author_id
3. Develop a rollback script to revert changes if necessary.
4. Plan and document the handling of existing data in the Tickets table to ensure data integrity and continuity.

Outcome

• The Tickets table will be updated with three new optional fields: ticket_group, author, and author_id.
• The migration will be fully reversible with a rollback script.
• The database performance will be maintained or improved due to the addition of necessary indexes.

Acceptance Criteria

• The Tickets table includes new columns: ticket_group, author, and author_id.
• Indexes are applied to ticket_group and author_id.
• A rollback script is available and tested.
• Migration script is created for review in PR

[humansinstitute]

Assign on Hive Bounties Tribe only.

[aliraza556]

@humansinstitute Please assign me?

[saithsab877]

@humansinstitute I can help?

[AhsanFarooqDev]

@humansinstitute can I help?