You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a User in IRIDA Next, I want the results of a pipeline I ran to be available to another user in my group, so that they can access my results and proceed with the workflow.
Acceptance Criteria
While creating a Workflow Execution the user should see a checkbox at the bottom which says something like Share with Project or Share with Group, depending on the namespace type that the user selected samples from
If the checkbox is selected this should set a shared_with_namespace boolean to true in the workflow_execution model
While viewing Workflow Executions from a Project, workflow executions with shared_with_namespace set to true where namespace_id matches the project namespaces id should also appear in the table
These workflow executions that are shared should not be deletable, but could be exportable
A user with view_workflow_executions? permission in the namespace that the workflow execution was shared with should be able to view the workflow execution, but they should not be able to modify it in anyway.
The text was updated successfully, but these errors were encountered:
Summary
As a User in IRIDA Next, I want the results of a pipeline I ran to be available to another user in my group, so that they can access my results and proceed with the workflow.
Acceptance Criteria
Share with Project
orShare with Group
, depending on the namespace type that the user selected samples fromshared_with_namespace
boolean to true in theworkflow_execution
modelshared_with_namespace
set to true wherenamespace_id
matches the project namespaces id should also appear in the tableview_workflow_executions?
permission in the namespace that the workflow execution was shared with should be able to view the workflow execution, but they should not be able to modify it in anyway.The text was updated successfully, but these errors were encountered: