Bug GUI Workflow Requests Tickets.without tasknumber

[alf-cactus]

In GUI Workflow Requests Tickets. If you create a ticket with tasks with API and passed no tasknumber:

The Ticket is written to database but breaks the GUI. No more tickets, even valid ones, are displayed.

Fix: remove the ticket via API

Solutions: Either make tasknumber mandatory (@alf-cactus could do that) or change GUI behavior

[tpurschke]

@abarz722 what do you think - is there any contra-indication regarding mandatory task numbers from your side?

not sure if solving this on the db side with triggers is a better solution - https://chatgpt.com/share/67338b0d-058c-8007-a500-348e56d6a449

[abarz722]

As the task number is only used as a sort criterion, a default value of 0 would probably be sufficient for the beginning. I have several tickets with all task numbers 0 in my database without causing problems.

[tpurschke]

@abarz722 could we not simply drop the task_number and use the id of the reqtask table for sorting assuming tasks are created in the correct order?
So we would just have to generate the task number actually displayed (in the UI) - similar to the rule number.