ideas for ui improvements #6247
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
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:
4a. You can see which flow is being executed in a work queue by clicking a work queue
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.
The text was updated successfully, but these errors were encountered: