ticket-rework-status #29
@@ -8,18 +8,6 @@
|
||||
- app/Http/Requests/UpdateProjectTicketRequest.php and other ProjectTicket only to Ticket...
|
||||
- mehrere actions/quereys in services auslagern
|
||||
|
||||
#### Ticket Status
|
||||
- one ticket status can't have two bord_columns.
|
||||
- one bord_column can have multiple ticket statuses.
|
||||
- if a board_colum has multiple ticket status, it must be selected in wich status the ticket should be moved, if the ticket is moved to this column
|
||||
- replace board_colum_id on ticket with ticket status id
|
||||
- ticket status has an n:m relation in which relation the ticket can switch
|
||||
- frontend change ticket move to board colum to ticket move to status and show all allowed statusses.
|
||||
- backlog is thread like a board_column. the backlog can have also multiple tikcet statusses, that are not included in another column.
|
||||
- while creating a ticket in the backlog a new dropdown for the ticket status should be added
|
||||
- while creating a new board column a same named (Str::slug(name)) ticket status will be created for the new column
|
||||
- the last ticket type for a column/backlog cant be delteted
|
||||
|
||||
#### later
|
||||
- repository_connections check base Url maybe unnessecary?
|
||||
- Git listBranches replace baseUrl, owner, rperoName with GItReprository
|
||||
|
||||
Reference in New Issue
Block a user