-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow Executions: Share results #895
base: main
Are you sure you want to change the base?
Conversation
2d4b702
to
0115044
Compare
This comment has been minimized.
This comment has been minimized.
93d1b1a
to
493bce6
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments below to start and also some clarification questions (maybe geared more towards @ericenns :
- I would think we need a Workflow Execution listing for groups now? I don't see anywhere to view a workflow that's been shared with the group
- Should the user that created a shared workflow still be able to cancel/delete/modify the workflow from their own personal workflow listing?
- Listing the user that created the shared workflow on the workflow summary tab?
Also, could the description header for the project workflow executions page be updated as it no longer pertains to only automated workflows:
|
d639df0
to
cb092a5
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments on implementation. I have not tried creating an automated workflow execution but we should ensure that the shared_with_namespace
checkbox is not shown when creating an automated workflow execution as that would be confusing to the users.
samples: Sample.none, | ||
allowed_to_update_samples: true, | ||
namespace_id: @project.namespace.id, | ||
fields: nil, | ||
instance: @automated_workflow_execution | ||
instance: @automated_workflow_execution, | ||
namespace_type: @project.namespace.type, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick (blocking): based off of comment above, this does not need to be passed in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed in 02741a9
...iews/projects/automated_workflow_executions/_new_automated_workflow_execution_modal.html.erb
Outdated
Show resolved
Hide resolved
app/views/workflow_executions/submissions/create.turbo_stream.erb
Outdated
Show resolved
Hide resolved
81c9d5b
to
ab067fb
Compare
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some more comments below.
Maybe out of scope of this PR (@ericenns) but users with access to shared workflows are unable to export them which I imagine is part of the reason for sharing workflows?
<div class="flex items-center h-5 mb-4"> | ||
<% if [email protected] && @namespace_type %> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you flip these (and their closing tags) so that you don't render the empty div
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 4628876
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're also correct that the other project members should be able to export. Should be fixed in 85f9079
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Building on this, could you fix the path within the export preview to navigate to the workflow within the project if it's shared:
Currently it will navigate to the workflow as if it's owned by the user (which would be inaccessible), but if shared, we want to access it through the project (hopefully that makes sense).
Please also add associated UI tests for creating export from a shared workflow and clicking a shared link navigates to the expected page. There are similar tests in test/system/data_exports_test
that you can draw from.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One more comment while playing around
This comment has been minimized.
This comment has been minimized.
Code Metrics Report
Code coverage of files in pull request scope (98.5%)Reported by octocov |
What does this PR do and why?
Describe in detail what your merge request does and why.
This PR relates to STRY0016470, where we want to be able to share our workflow execution results to the project/group so that members are able to see the results. This PR covers issue #884
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other pull requests.
![image](https://private-user-images.githubusercontent.com/17057809/402659049-18054ce2-68e6-40a3-a7fa-7fb99dfd5508.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4Mzk0NjgsIm5iZiI6MTczODgzOTE2OCwicGF0aCI6Ii8xNzA1NzgwOS80MDI2NTkwNDktMTgwNTRjZTItNjhlNi00MGEzLWE3ZmEtN2ZiOTlkZmQ1NTA4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA2VDEwNTI0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc1OTY0NDExMTZmNGQ5NDAyOTg4MjZiYzIwMzVkYjliZTkyMDQ4NjlmMDlmZjU1MDgzNGRkMzk2NWUwMWViM2EmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ederY5sjuLGoNAiK8V6qwNF5bOPiNoQVkYT6tZR2Clc)
![image](https://private-user-images.githubusercontent.com/17057809/402659261-f02b696c-cc6c-4849-8238-e617af349dfb.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg4Mzk0NjgsIm5iZiI6MTczODgzOTE2OCwicGF0aCI6Ii8xNzA1NzgwOS80MDI2NTkyNjEtZjAyYjY5NmMtY2M2Yy00ODQ5LTgyMzgtZTYxN2FmMzQ5ZGZiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA2VDEwNTI0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc3ZjM0NzkxNjI0N2E5ZTRiN2FhNjQ5MzFmNWE5ODkxNzMwMzlmNmViNjFhZWEyODE2ZTRmNWFkZDI3ZDZiMDcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.qud-zeceBgPNc48b0bLB0FMRgOk0BKuJ1ogDNH1AgaI)
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
PR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.