-
Notifications
You must be signed in to change notification settings - Fork 666
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
[UI Feature] Filtering by kickoff_time
#3943
Comments
can you assign me this issue? |
@nik132-eng Are you still working on the issue? |
It's good first issue but I don't get the proper idea project you can work on this issue. |
Hello @samhita-alla , can I be assigned this issue, please? |
We'll give preference to the contributor who submits the first PR. |
Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. |
Motivation: Why do you think this is important?
As a user, I would like to know which scheduled runs failed base on the
kickoff_time
, so that I can know which execution window requires remedy actions.Currently the UI shows execution sorted by
start_time
, with the ability to filter by status/version/start time/duration.For running scheduled pipeline, we indicate the
kickoff_time_input_arg
in launchplan.Currently there is no view base on
kickoff_time
also it can be error prone or cumbersome to click on every execution "Inputs/Outputs" to view thekickoff_time
. Since this is largely used in launchplan, it would help to have the list of execution sorted base onkickoff_time
to know if a particular scheduled execution failed and wasn't remedied.Goal: What should the final outcome look like, ideally?
Ability to sort or filter by
kickoff_time
in the UI. Executions without this arg can be omitted from view.Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: