Linking tickets & ticket viewing rework

[jkingster]

Feature request: Linkable tickets. On certain tickets, they may be related to OTHER tickets. This feature would allow you to link ticket(s) to other ticket(s), allowing you to cross view without searching for it entirely. As long as you know the ID and/or the title of the ticket, you would be able to link it directly. This would allow searching for tickets more efficient.

This would require a new SQL table, so a flyway migration would be necessary. Below is a possible example of the table schema:

CREATE TABLE IF NOT EXISTS TICKET_LINKS
(
   ID INTEGER PRIMARY KEY AUTOINCREMENT,
   TICKET_ID INTEGER NOT NULL REFERENCES TICKET(ID),
   LINKED_TICKET_ID INTEGER NOT NULL REFERENCES TICKET(ID)
);

It's pretty standard, but would allow multiple tickets to be linked. Since SQLite does not support arrays out the box.

The next idea would be completely reworking how tickets are viewed. Right now it's hideous IMO and could use some UI updates. Even increasing the size of the screen I think would be more beneficial. The update features could use some work as well, along with adding filters to employee lookup.

[jkingster]

This is how the viewer looks currently in development. The bottom three squares represent linked tickets, linked documents(?), and the other is undefined. Not sure if this will remain, I needed to fill some gaps. A new field will be the resolved by.

SQL query will be something along these lines:

ALTER TABLE TICKET ADD COLUMN RESOLVED_BY DATETIME NOT NULL DEFAULT '0/00/0000'

Or something along those lines.

[jkingster]

This is being implemented in v1.1.0, see here: https://github.com/jkingster/QuickTicket/tree/v1.1.0