At this point of the development, we want to ensure that what was put in place in story #13230 works with several fields.

Functional Overview

Contributor semantic

The Contributor semantic evolves to its final form.

When no semantic is defined, the tracker admin can choose to either

• Regular semantic: Select one field amongst the "users" lists fields
• Automated semantic: All list fields (select box, multi select box, checkbox, radio button) bound to users are taken into account.
  • In this case, for the features bellow, the list of fields that are taken into account are computed dynamically everytime we need it. This way we don't have to maintain the list of fields and manage their addition / removal.
  • This can come with a perf penalty but this should be verified first (make it works, make it correct, make it fast).

When automated is selected, its still not possible to switch back.

For admin who switch to automated with the previous story, they are moved automatically to "Automated semantic" without further configuration.

Permissions

No change for the configuration.

The enforcement of the permissions now takes into account all list fields as described in the previous section.

Tracker TQL

No change in the syntax.

The @assigned_to will look for values in all list fields as described in the previous section.

Cross Tracker Search TQL

No change in the syntax.

The @assigned_to will look for values in all list fields as described in the previous section.

My Artifacts Widget v2

No change in the display

All list fields as described in the previous section are taken into account for the display of artifacts.