Hi everyone,
Managed to do this : tickets assigned to a specific group are automatically
closed.
The purpose is to deny the possibility for requesters to reject the proposed
answers from this group.
To achieve this the solved status is disabled from the lifecycle of the group.
But this requires a few modifications :
- in the function canSolve from ticket.class.php :
https://gist.github.com/OlivierLM/9a487f330a5ce649b406
- in the pre_updateInDB from commonitilobjct.class.php :
https://gist.github.com/OlivierLM/4c81993d93e1befb7010
Thanks to Alexandre for puting me on the track of autoclosedelay :)
----- Mail original -----
> > >>> ----- Mail original -----
> > >>>> De: "Olivier Le Monnier" <[email protected]>
> > >>>> À: "Liste de diffusion des utilsateurs de GLPI" <[email protected]>
> > >>>> Envoyé: Mercredi 3 Février 2016 09:59:25
> > >>>> Objet: [Glpi-user] Passage automatique à Clos
> > >>>>
> > >>>> Hi all, for some legal reasons (silence equals acceptance), we'd
> > >>>> like
> > >>>> tickets assigned to a specific group to automatically get their
> > >>>> status changed from solved to closed.
> > >>>> The purpose is to deny the possibility for requesters to reject the
> > >>>> proposed answer.
> > >>>>
> > >>>> The first considered solution was to remove the solved status from
> > >>>> the
> > >>>> lifecycle of the group, but in this case, the group can't even set a
> > >>>> solution.
> > >>>>
> > >>>> The second hypothsesis was to set a business rule to automatically
> > >>>> to
> > >>>> change the status from solved to closed for the group, but the
> > >>>> status
> > >>>> doesn't appear in the list of criterias.
> > >>>>
> > >>>> Any idea ?
> >
> > > In this case, a business rule cound permi this. Two problems remain :
> > > - status doesn't appear in the criterias, this can be fixed quite esaily
> > > :
> > > see https://gist.github.com/orthagh/6c9b813e72b6a175c81b
> > > - the groups of the ticket can be targeted in the rules only when they
> > > are
> > > changed (roughly, they are not in the input of the rule when another
> > > field
> > > is changed)
> >
> > Thanks a lot ! I was about to get the first point before lunch…
> >
> > Is there anything I can do as easily to workaround the second point (the
> > assigned group doesn't get into the input for the rule because it is
> > unchanged ?)
> >
> > I keep searching…
>
> Could it be as easy to add a criteria for the business rule that would turn
> the status from solved to closed on the presence of a non-null solution ?
>
> --
> Olivier Le Monnier — ☎ 023156.6209
> Administrateur systèmes libre(s)
> Direction du Système d'Information
> Université de Caen Normandie
>
>
> _______________________________________________
> Glpi-user mailing list
> [email protected]
> https://mail.gna.org/listinfo/glpi-user
--
Olivier Le Monnier — ☎ 023156.6209
Administrateur systèmes libre(s)
Direction du Système d'Information
Université de Caen Normandie
_______________________________________________
Glpi-user mailing list
[email protected]
https://mail.gna.org/listinfo/glpi-user
