Skip to content
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

Open
wants to merge 31 commits into
base: main
Choose a base branch
from

Conversation

malchua
Copy link
Contributor

@malchua malchua commented Jan 13, 2025

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
image

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Login as a user that is a member of a group.
  2. Select a project within that group.
  3. In the samples page for that project, create a workflow execution and check the box asking if you want to share the results with the project members.
  4. After creating the workflow execution, click on the Workflow Executions section on the sidebar of that project.
  5. Confirm that the workflow execution is present.
  6. Log out, then login as a different member that has access to the same group (the access level must be at least an Analyst)
  7. Go to the Workflow Executions page for the same project.
  8. Confirm that this member is also able to see the same workflow execution.
  9. Confirm that this member is not allowed to Cancel, Delete, or Edit this workflow execution.

PR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

@malchua malchua force-pushed the workflow_execution/share_results branch from 2d4b702 to 0115044 Compare January 13, 2025 19:08

This comment has been minimized.

@malchua malchua force-pushed the workflow_execution/share_results branch from 93d1b1a to 493bce6 Compare January 27, 2025 04:35

This comment has been minimized.

@malchua malchua marked this pull request as ready for review January 27, 2025 14:39
Copy link
Collaborator

@ChrisHuynh333 ChrisHuynh333 left a 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 :

  1. 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
  2. Should the user that created a shared workflow still be able to cancel/delete/modify the workflow from their own personal workflow listing?
  3. 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:
image

Comment on lines +118 to +131
class:
"w-4
h-4
mr-2.5
text-primary-600
bg-slate-100
border-slate-300
rounded
focus:ring-primary-500
dark:focus:ring-primary-600
dark:ring-offset-slate-800
focus:ring-2
dark:bg-slate-700
dark:border-slate-600",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you move these onto a single line. We've been moving class lists like these to a single line to prevent this endless 'tabbing' of the classes.

@@ -3,7 +3,7 @@
require 'application_system_test_case'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a UI test verifying the expected absence of the shared workflow row actions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants