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

Enhance Workflow Display with Comprehensive Listing, Grouping, and Advanced Filtering #670

Open
ynixon opened this issue Mar 31, 2024 · 2 comments

Comments

@ynixon
Copy link

ynixon commented Mar 31, 2024

Is your feature request related to a problem? Please describe.
The current display on GitActionBoard provides a high-level view of the status of GitHub workflows, which is useful but not comprehensive for teams managing numerous workflows across various repositories. The absence of detailed information like the triggering event and the user who triggered the workflow makes it harder to quickly understand and act on workflow statuses, especially in complex project environments.

Describe the solution you'd like
I propose an enhancement to the workflow display that introduces a list view with additional columns for more detailed insights. The proposed columns are:

  • Repository: Name of the repository where the workflow resides.
  • Status: Current status of the workflow, color-coded for quick visual reference.
  • Last Run: Timestamp of the last run, providing insight into recency.
  • Event Triggered: Type of event that triggered the workflow, such as "Scheduled", "Push", "Pull Request", etc.
  • User: The user who initiated the workflow, useful for identifying who made the changes or manually triggered the workflow.

In addition to these columns, the following features would significantly enhance the tool's utility:

  • Group by Repository: Allows grouping workflows by repository, with collapsible sections for each repository to efficiently manage screen space.
  • Filtering Options: Filters for repository name, workflow status, event triggered, and user, enabling users to narrow down to specific workflows of interest.
  • Column Sorting: Capability to sort the list based on any column, facilitating easier organization and navigation through workflows based on various criteria like the most recent run, status, or user.

Describe alternatives you've considered
An alternative could involve using separate tools or scripts to extract and display this information. However, integrating these features directly into GitActionBoard would offer a seamless and centralized experience for monitoring and managing GitHub workflows, eliminating the need for additional tools and processes.

Additional context
Incorporating these enhancements would empower teams, especially those with multiple workflows and repositories, to have a more detailed and actionable overview of their CI/CD pipeline statuses. This improvement aims at not just monitoring but also at effectively managing and troubleshooting workflows by providing all necessary details in one comprehensive view.

Copy link

boring-cyborg bot commented Mar 31, 2024

Thanks for opening your first issue here! Be sure to follow the issue template!

@sumanmaity1234
Copy link
Collaborator

Hi @ynixon,
Repository Name, color coded status and last run information is already available in GitAction Board. Additionally, people can filter the workflows based on workflows or triggered event. You can already check the example of https://otto-de.github.io/gitactionboard/#/workflow-jobs.

The other requested feature like having a table view, it might be good to have feature but I am not sure if it'll add much value or not.

As per my understanding people are mainly concern when pipeline is red. If a certain pipeline is red, then you can just click on the tile and it'll redirect you to the github workflow run page where all the suggested information along with some more will be available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants