At the moment the role assignment in Users > Projects is made via a convenient set of dropdown selects, nicely populated with the currently selected project category and/or project.
Role assignment is however done differently in Projects > Users and Account & Settings > Administrators.
For consistency it might thus be better to also use a drag and drop approach in Users > Projects as well [alternatively, if this solution looks imbalanced, we can also consider using a tree for the selection of the role, as used in the Test Cycle assignment to Test Instance (but I believe we went from selection trees to drag and drop in the other cases)]
Also, depending on how the users define the roles, in practice it might be that a given user will mostly only get one role per project. The pre-selection of the project is then less useful.
A bug has been introduced lately and the project role assignment is currently broken.
Instead of fixing it, it might be beneficial to implement the design change proposed above.
At the moment the role assignment in Users > Projects is made via a convenient set of dropdown selects, nicely populated with the currently selected project category and/or project. Role assignment is however done differently in Projects > Users and Account & Settings > Administrators. For consistency it might thus be better to also use a drag and drop approach in Users > Projects as well [alternatively, if this solution looks imbalanced, we can also consider using a tree for the selection of the role, as used in the Test Cycle assignment to Test Instance (but I believe we went from selection trees to drag and drop in the other cases)] Also, depending on how the users define the roles, in practice it might be that a given user will mostly only get one role per project. The pre-selection of the project is then less useful.