All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Fix undefined index
- Prevent business rules from triggering twice on tickets
- Handle mandatory template fields in history button escalation
- Fix
tagdeletion before escalation usingEscalate button - Fix
labelbutton color
- Fix compatibility check with Behaviors plugin
- Fix path to ajax files in javascript files
- Fix: allow groups from recursive parent entities to be considered when adding a user to a ticket
- GLPI 11 compatibility
- Fix template mandatory field validation interference when adding solutions to tickets
- Fix the relationship when cloning a ticket: if the
Close linked tickets at the same timeoption is enabled, the relationship isDUPLICATED_WITHotherwise it'sLINK_TO - Fix tech assignment should not trigger escalation behavior (as defined in the documentation)
- Rename options related to ticket cloning and closure to avoid ambiguity
- Fix rule doesn't trigger when user uses "Assign myself" button
- Improved access control checks when cloning ticket
- Fix duplicate notifications being sent during escalation by implementing two additional targets.
- Fix 8 warnings in the
php-errors.logfile - Fix reopening of a cloned ticket when the parent ticket is reopened
- Fix ticket task not added to timeline during escalation
- Fix Escalate timeline button execute RuleTicket
- Fix group assign with
reassign_group_from_catoption - Fix the
remove_techoption when a user was added to a ticket
- Fix
show_historyoption when using theEscalatebutton. - Fix
use_assign_user_groupoption wich delete assing users - Fix
ticket_last_statusoption when using theAssociate myselfbutton.
- Calculation of status when a technician self-assigns to a ticket
- Fixed
Bypass filtering on the groups assignmentoption - Fixed technician deletion when ticket updated
- Fixed
Ticket status after an escalationoption - Do not perform escalation when mandatory ticket fields are missing
- Ensure that when several technicians are assigned, they are treated correctly during the escalation.
- Redirect users without ticket rights after escalation.
- Fix private task added when ticket mandatory fields are not filled
- Remove redundant notifications
- Fixed assignment of requester group to ticket
- Ensure plugin works seamlessly in external contexts (e.g., from plugins)
- Fixed
Close cloned tickets at the same timeoption - Fixed
Bypass filtering on the groups assignmentoption - Rename the option "Don't change" to "Default (not managed by plugin)" for the "Ticket status after an escalation" setting to reduce ambiguity.
- Remove the user when a ticket escalates to a group with
remote_tech optionset totrue
- Check permissions before displaying group history or escalating access
- Prevents undefined index
commentwhen escalating
- Remove redundant notifications
- Correction of the task message generated during escalation
- Fix task not added when escalating with history
- Fix escalating with history
- Fix
statusafter escalation - Prevent anonymous user to be deleted during escalation
- Prevent an escalation when a ticket is updated
- Full history window (now is a modal)
- Add config option for default assignation
- Fix rules execution before escalation
- Set
assign as observerunchecked by default - Fixed
blocking of user deletion - Fix
use technician groupoption
- Fix
Display delete buttonoption
- Fix unauthorized deletion of ticket actors according to plugin configuration
- Fix unsended notifications while
Delete old groups when adding a new oneis set toNo
- Fix behavior for
Ticket status after an escalationoption - Fix cloning error display
- Fix group filtering
- Add short label for split action buttons in timeline footer
- Fix group dropdown depending on the configuration
use_filter_assign_group - Fix permission checks in ticket escalation
- Fix group filtering in escalation process