Content
View differences
Updated by Marcello Rocha Pereira 11 months ago
When defining or editing a custom action with a multi-select user field, we are presented with 2 issues that are also related:
1. The **assign to executing user** placeholder is never rendered, even if set.
2. Impossible to assign to more than **one user**
3. If attributed to a specific user, when saving we are greeted by a server error (500)
The expected behaviour is:
1. Being able to assign multiple users to the action
2. The user names, or the executing user placeholder, being rendered in the field.
<br>
#### **Reproduction Steps**
1. Have a custom field of type **User** with _Allow multi-select_ MULTI\_SELECT\_NAME enabled
2. Create a Custom Action and add an action for the custom field above
3. Save the action
4. Go to edit the action and note that the Assign to executing user text won't be rendered
5. Try to assign any specific user
6. Save the action
7. Appreciate the error message
Steps 3 and 4 can be omitted, but this was the rundown when the bug was detected
#### **OpenProject version**
_Detected on 16.0, introduced around 15.4_
1. The **assign to executing user** placeholder is never rendered, even if set.
2. Impossible to assign to more than **one user**
3. If attributed to a specific user, when saving we are greeted by a server error (500)
The expected behaviour is:
1. Being able to assign multiple users to the action
2. The user names, or the executing user placeholder, being rendered in the field.
<br>
#### **Reproduction Steps**
1. Have a custom field of type **User** with _Allow multi-select_
2. Create a Custom Action and add an action for the custom field above
3. Save the action
4. Go to edit the action and note that the Assign to executing user text won't be rendered
5. Try to assign any specific user
6. Save the action
7. Appreciate the error message
Steps 3 and 4 can be omitted, but this was the rundown when the bug was detected
#### **OpenProject version**
_Detected on 16.0, introduced around 15.4_