Describe the bug
LORIS allows instruments to use instrument permissions where access to specific instruments can be checked based on a project-specific permission code. This works well to restrict access to a specific instrument in a timepoint but maintain access to the rest of the instruments in the same timepoint
Issue: If a user who does not have the instrument permission tries to "start next stage" the battery will still be populated but a 500 error will be displayed to the user. After a refresh the intrument_list module will be populated regardless...
What did you expect to happen?
The battery should be populated without error, it's only access to the instrument that should be restricted, not it's creation
Describe the bug LORIS allows instruments to use instrument permissions where access to specific instruments can be checked based on a project-specific permission code. This works well to restrict access to a specific instrument in a timepoint but maintain access to the rest of the instruments in the same timepoint
Issue: If a user who does not have the instrument permission tries to "start next stage" the battery will still be populated but a 500 error will be displayed to the user. After a refresh the intrument_list module will be populated regardless...
What did you expect to happen? The battery should be populated without error, it's only access to the instrument that should be restricted, not it's creation