Group managed OLA

[SebSept]

Group managed OLA

Checklist before requesting a review

Please delete options that are not relevant.

• [x] I have read the CONTRIBUTING document.
• [x] I have performed a self-review of my code.
• [x] I have added tests that prove my fix is effective or that my feature works.
• [ ] This change requires a documentation update.

Description

Specifications

• multiple OLA can be associated to a ticket (no more just a single tto and a single ttr)
• ola due dates cannot be set manually anymore in a ticket
• the same ola can be associated multiple times to a ticket, if one is completed.
• old form params are still supported (olas_id_tto, olas_id_ttr)
• ola must be associated with a group (if the group has the ability to be assigned to a ticket)
• ola previously created (without group) can be associated to tickets
• ola can be associated to ticket by rule and form at the same time
• completion :
  • tto :
    • when ticket is "taken into account" (add task, add followup) by a user of the ola group
    • when a user of the dedicated group assign itself (or it's group) to the ticket.
    • when a group associated to ola is removed from ticket assigned group
  • ttr :
    • when the ticket is closed or solved
    • when a group associated to ola is removed from ticket assigned group
• due time delaying :
  • ttr : when the ticket status is WAITING
  • tto : when the ticket status is WAITING and ticket is not assigned to group
• due_time is not updated on ticket's date update
• ticket is late if :
  • end_time is defined and > due_time
  • end_time is not defined & due_time is passed
  • ticket status is not WAITING

[PierreTeclib]

@SebSept :

Small issue. This field doesn’t seem relevant here:

Moreover, when a change is made and a date is displayed, the calendar icon on the right does nothing when clicked.

[SebSept]

this is a readonly datetime input, not the best option.

I just removed this field from display.