Transfer _actors input into historical input keys

[cedric-anne]

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

[cconard96]

Isn't the "Assign" action for actors in rules supposed to replace all previous actors of that type with the one specified?
Right now, Assign is acting the same as Append.

[AdrienClairembault]

Isn't the "Assign" action for actors in rules supposed to replace all previous actors of that type with the one specified? Right now, Assign is acting the same as Append.

I've noticed the same behavior yesterday on GLPI 9.5 so It may be an old bug not related to @cedric-anne changes.
Still would be nice to fix it thought ;)

[cedric-anne]

I've noticed the same behavior yesterday on GLPI 9.5 so It may be an old bug not related to @cedric-anne changes.
Still would be nice to fix it thought ;)

assign only act on actors being added by current ticket update. If actors were already existing before the update process, they are not remove. We agreed, with @orthagh, to not change this behaviour for now.

[cedric-anne]

There is some issues when using formcreator plugin. I have to investigate.

[cedric-anne]

There is some issues when using formcreator plugin. I have to investigate.

Fixed in last commit.

[btry]

The current state of the PR seems to work fine with he current revision support/2.13.0 of Formcreator. Anyway, I finished a PR in the plugin which cleans the actors before creating an ITIL object. (pluginsGLPI/formcreator#2857)

I thikn it is worth to merge as at least this plugin will no longer generate weird data and will no longer cause problem if there is need to upgrade the core.