[UI] Allow users to filter pipeline runs by status

[shotarok]

We can filter pipeline runs by name on the KFP UI but we can't filter them by status because of the following code.

https://github.com/kubeflow/pipelines/blob/c8c9905bf2b2662a851c339afbd143cfdbdb603c/frontend/src/components/CustomTable.tsx#L515-L527

This feature allows users to see the failed pipeline only.

[Bobgy]

Thanks for the feature request, this is a very useful feature. I believe we've supported more fields for the filter at the API layer, it'll be great if UI supports that too.

The major problem is designing either:

• the syntax to specify the filter
• UI elements that allow users compose the filter

[Bobgy]

Welcome contribution to define an ideal UX.

[shotarok]

I like the query syntax like GitHub, which is expressed by a list of <qualifier>:<value>. One drawback is that it can't express IN and IS_SUBSCRING although it's able to deal with EQUALS, NOT_EQUALS, GREATER_THAN, GREATER_THAN_EQUALS, LESS_THAN, and LESS_THAN_EQUALS.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[pyxelr]

/reopen

Hi, is there a chance that this functionality (to filter Kubeflow runs by status within Kubeflow UI) has been already implemented? If not, are there any plans to do it for the next versions?

[google-oss-prow[bot]]

@pyxelr: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Hi, is there a chance that this functionality (to filter Kubeflow runs by status within Kubeflow UI) has been already implemented? If not, are there any plans to do it for the next versions?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[shotarok]

/reopen

@pyxelr No, I'm afraid the current master branch also has the same logic as the previous. I'll try to reopen this issue. https://github.com/kubeflow/pipelines/blob/85c7901874f19b6e7ecf6e1b152f53ab429e6edc/frontend/src/components/CustomTable.tsx#L519-L531

[google-oss-prow[bot]]

@shotarok: Reopened this issue.

In response to this:

/reopen

@pyxelr No, I'm afraid the current master branch also has the same logic as the previous. I'll try to reopen this issue. https://github.com/kubeflow/pipelines/blob/85c7901874f19b6e7ecf6e1b152f53ab429e6edc/frontend/src/components/CustomTable.tsx#L519-L531

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jlyaoyuli]

Hello @shotarok, We are still waiting for the community to define the UX behavior. Here is one of the example that we can explore to filter by status. https://react-select.com/home

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[avito-ds]

Can we try to add filter?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.