Fix auto assign played after rules in tickets

[RomainLvr]

Q	A
Bug fix?	yes
New feature?	no
BC breaks?	no
Deprecations?	no
Tests pass?	yes
Fixed tickets	!32840

• I create a business rule for tickets when they are added that, as soon as a technician group exists in the ticket, the ticket is assigned the status new.
• I assign a group responsible for the category.
• I set 'Automatic assignment of tickets, changes and problems' to "category then material" from my entity's support parameters.

When the ticket is created, the group assignments are correct, but the rule assigning a status to the ticket doesn't work.
This is due to the fact that the rule is launched before the automatic assignment in the ticket addition procedure.

[trasher]

Existing tests are broken.

Also, I'm not sure this kind of issue really can be handled right now; it should cause other issues to change the order of execution :(

[cedric-anne]

There is already a piece of code that is supposed to handle this case:

glpi/src/RuleTicket.php

Lines 206 to 210 in fae0c07

	// Special case of status
	if ($action->fields["field"] === 'status') {
	// Add a flag to remember that status was forced by rule
	$output['_do_not_compute_status'] = true;
	}

Could you check why it does not work ?

[RomainLvr]

There is already a piece of code that is supposed to handle this case:

glpi/src/RuleTicket.php

Lines 206 to 210 in fae0c07

	// Special case of status
	if ($action->fields["field"] === 'status') {
	// Add a flag to remember that status was forced by rule
	$output['_do_not_compute_status'] = true;
	}

Could you check why it does not work ?

Indeed this case was already treated and it works, the problem still lies in what is mentioned in this ticket: !32835

[RomainLvr]

There is already a piece of code that is supposed to handle this case:

glpi/src/RuleTicket.php

Lines 206 to 210 in fae0c07

	// Special case of status
	if ($action->fields["field"] === 'status') {
	// Add a flag to remember that status was forced by rule
	$output['_do_not_compute_status'] = true;
	}

Could you check why it does not work ?

Indeed this case was already treated and it works, the problem still lies in what is mentioned in this ticket: !32835

Finally, the first concern is that the rule is not executed at all, because one of the criteria required for this rule is not registered until after the rule has been attempted to be executed. As a result, the '_do_not_compute_status' is never set, and the status lock doesn't work.

[cedric-anne]

Same comment as in #16885. We have to deal with current rules engine limitations.