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

ideas for ui improvements #6247

Closed
marvin-robot opened this issue Aug 5, 2022 · 2 comments
Closed

ideas for ui improvements #6247

marvin-robot opened this issue Aug 5, 2022 · 2 comments
Labels
needs:triage Needs feedback from the Prefect product team status:stale This may not be relevant anymore ui Related to the Prefect web interface

Comments

@marvin-robot
Copy link
Member

Opened from the Prefect Public Slack Community

williamjamir: A couple of suggestions about the Prefect 2.0 UI

1- In a scenario where the flow has a required input, If we go to the Deployments page and just click Run the job fails, saying that it is missing a parameter.
In my opinion, if a parameter is required from the flow, it should not be possible to run a flow without informing the value.

2- It would be nice to change the default value from the deployment over the tab Parameters; that feels more natural than clicking on the three dots.

3 - On the work Queues section: would it be possible to check which agents are on?

4a - Over the Flow Runs, would be interesting to show on which “Work Queue” the task was executed.
4b - It would be nice to see the previous runs for each “Work Queue”, showing which Flow was executed on the given queue.

5 - Notification: Is it possible to add a notification when an agent/queue is off? (or when doesn’t have any agent waiting for upcoming requests for a given work queue).

6 - On the JSON Block, would be possible to show a history of modifications? Would be nice to easily identified when a modification was made with a diff showing the changes.

khuyen: Thanks for the great suggestions. We will definitely consider about these suggestions. Here are some thoughts on 3 of your suggestions:

  1. There is only one agent per work queue so I’m not sure why it would be helpful to check which agent is in a work queue
    4a. You can see which flow is being executed in a work queue by clicking a work queue
  2. Yes you can schedule when the agent is off. The flow just doesn’t run on schedule if the agent is not there

jenny: Hi <@U02JEA4LC8K> - thanks for the ideas. If it's ok with you I'm going to move this into an issue so we can track your suggestions and make sure they don't get lost.

For your #1 - there is some work happening right now to address that but we want to make sure we get the balance between reminders and restrictions right.

jenny: <@ULVA73B9P> open “ideas for ui improvements”

Original thread can be found here.

@zhen0 zhen0 added the ui Related to the Prefect web interface label Aug 5, 2022
@zanieb zanieb added the v2 label Aug 5, 2022
@zhen0 zhen0 added the needs:triage Needs feedback from the Prefect product team label Sep 18, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. To keep this issue open remove stale label or comment.

@github-actions github-actions bot added the status:stale This may not be relevant anymore label Mar 30, 2023
@github-actions
Copy link
Contributor

This issue was closed because it has been stale for 14 days with no activity. If this issue is important or you have more to add feel free to re-open it.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs:triage Needs feedback from the Prefect product team status:stale This may not be relevant anymore ui Related to the Prefect web interface
Projects
None yet
Development

No branches or pull requests

3 participants