Describe in detail what your merge request does and why.
This PR fixes a bug in the project_policy -> submit_workflow? method, which was passing in the project record instead of the project's namespace as is expected by the can_submit_workflow? and effective_access_level within the member.rb file.
Added a project_policy and system test to verify an analyst can submit a workflow through a namespace group link as that's how the issue was discovered.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other pull requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Login as user2@email.com
Create a group User2Group
Logout and login as user1@email.com
4 Create project under user namespace Project1
Create sample in project
Go to the project Members page and click the Groups tab
Invite group User2Group to the project with an Analyst access level
Logout and login as user2@email.com
Go into the Project1 (created in step 4) from the projects dashboard
Go to the project samples page and verify you can now select the sample, see the pipeline launch button, and launch a workflow
PR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
What does this PR do and why?
Describe in detail what your merge request does and why.
This PR fixes a bug in the
project_policy
->submit_workflow?
method, which was passing in the project record instead of the project's namespace as is expected by thecan_submit_workflow?
andeffective_access_level
within themember.rb
file.Added a project_policy and system test to verify an analyst can submit a workflow through a namespace group link as that's how the issue was discovered.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other pull requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
user2@email.com
User2Group
user1@email.com
4 Create project under user namespaceProject1
Members
page and click theGroups
tabUser2Group
to the project with anAnalyst
access leveluser2@email.com
Project1
(created in step 4) from the projects dashboardPR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.