Fix - Handle mandatory template fields in history button escalation #392
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist before requesting a review
Please delete options that are not relevant.
Description
History button escalation now works correctly when "Assigned Group" field is mandatory in ticket template.
Problem
When escalating a ticket via the history button (
climb_group()) with mandatory template fields (especially "Assigned Group"), the validation failed with error:Root Cause
The
climb_group()method only passed minimal data (_itil_assign) toTicket->update(), which triggered template validation without the required fields.Solution
Modified
climb_group()to pass comprehensive ticket data including:_itil_assignand_groups_id_assignformats (required for rules execution and template validation)Screenshots (if appropriate):