-
Bug
-
Resolution: Fixed
-
None
-
High
-
Opening read-only tasks via URL leads to a no access exception.
-
Emptyshow more show less
problem
Opening the task via URL /editor/task/123ID returns a no access exception if the user is assigned read only to the job.
Reason is, that the JS code tries always to open the task in the status edit which is invalid in this situation. Before 7.19.0 this was allowed, now it is prevented by the advanced rights check of the job coordinator functionality.
solution
Make the openTaskDirect method in the UI more intelligent to choose the correct state to be used.