Skip to content

Branch View Filtering by Success/Failed #367

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

Open
AleksandarCole opened this issue Jun 9, 2025 · 0 comments
Open

Branch View Filtering by Success/Failed #367

AleksandarCole opened this issue Jun 9, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@AleksandarCole
Copy link
Collaborator

Is your improvement proposal related to a problem? Please describe.

Users trying to improve CI reliability need to periodically review why pipelines are failing and manually sift through results to spot trends. Currently, the branch view (where users can see all workflows) doesn't have filtering options, making it difficult to filter down to only pipelines that have failed. This manual process is time-consuming and makes it harder for users to identify patterns in failures.

Describe the solution you'd like

Note: The current branch view displays workflows, which don't have a pass/fail state - only the pipelines within workflows have states. Therefore, filtering by success/failed status cannot be added to the existing workflow view.

Instead, introduce a toggle or selectable option on the branch page that allows users to switch between:

  • Workflow view (current view) - Shows all workflows without state filtering
  • Pipeline view (new view) - Shows all executed pipelines with filtering capabilities

The new pipeline view would include:

  • Filter by pipeline state (passed/failed/stopped/etc.)
  • Filter by timeframe (last 24 hours, last week, custom date range)
  • Filter by pipeline duration
  • Potentially combine multiple filters for more targeted analysis

This would enable users to quickly identify failing pipelines and analyze trends without manually reviewing every workflow.

Describe alternatives you've considered

No response

Additional context

Since workflows themselves don't have a pass/fail state (only the pipelines within workflows have states), the solution needs to focus on pipeline-level filtering rather than workflow-level filtering.

@VeljkoMaksimovic has additional context for this, as we were reviewing our options for 1.3 release and this popped up when discussing branch datetime filters.

@AleksandarCole AleksandarCole added the enhancement New feature or request label Jun 9, 2025
@github-project-automation github-project-automation bot moved this to Backlog in Roadmap Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant