Project field disappears when target project disallows user to edit the project
|Assignee:||Jean-Philippe Lang||% Done:|
- Editing the Project Field in an Issue reloads the form
- On Reloading / Rendering the project field is excluded if the user is not allowed to change the
project_idfor issues in that project
- The field disappears when the user clicks on a project where changing the project field is not allowed
- The issue cannot be moved to the other project by that user, however: The list of target projects is calculated by the right to create issues in that project. This means that there is a mismatch.
The project field should not disappear on selection of a project, either by showing the field more often (lax approach) or reducing the target projects list.
My suggestion for the lax approach is:
Project field disappears when target project disallows user to edit the project (#24311).