How to reproduce:
- Create an nFeed field
- Set context on a sub-task issue type
- Make the field mandatory in the test project
- Create two sub-tasks
- Bulk edit the two sub-tasks
- Tic the "Change <nfeed field name>" checkbox but do not select a value
- Click on next button
The BulkEditDetailsValidation page is reloaded and the field is highlighted because a value on this field is mandatory. An error (403) says the request is valid but the server is refusing action.
No error should be displayed when the page is reloaded, the user shoud be able to set a value.
If no issuetype context is set (all issuetype) the field is populated when the validation fails because of mandatory field not set.
The bug is not present when a project context is set.