Navigation restructure (Dashboard 2.0)

[Venefilyn]

Description

Going from packit-service to individual results within the Packit dashboard is great and works as it should. It shows the extend of what is possible from things like Testing Farm

However, if you want to go to the Packit dashboard to view anything else, from a package maintainer there is very little that can be viewed for my project without a lot of hassle or trouble finding them.

As a Packit maintainer, it is however a perfect view as it shows everything happening regarding Packit and its services

---

For this reason, there is work to be done to make more parts of the application better for both parties, we already have some things planned like

• Make it possible to filter the list of jobs by a time range #257
• Aggregated views #196

But for a completely usable system by package maintainers we need to restructure the navigation and relationship between projects and their builds and runs

Structure proposal

With a context selector we could put it in the top banner or move it to the top of the sidebar. Within it, we would show projects and allow the user to search for their projects. With a default option being "All projects" which would mean everything functions like how it is now

With the context selected for a specific project, e.g. packit/dashboard

• Jobs would be filtered to only include builds and tests triggered from this repo
• Pipelines would be filtered as well to only include pipelines triggered by this repo
• Projects would show a selection of the current project and allow you to select a different project from there as well

With the context cleared, going for All projects

• Jobs would show all builds and tests as it dows now
• Pipelines would show the latest pipeline from any project
• Projects would show all the projects and allow you to search and select a project for the context

Routes themselves should change with this as well, with previous ones either redirecting or being kept for all-projects

• /projects - Current projects list that already exists
• /projects/packit/dashboard - Same as above but keeping data about the selected project
• /projects/packit/dashboard/detail - the project view itself
• /projects/packit/dashboard/jobs
  • /projects/packit/dashboard/jobs/copr-builds
  • /projects/packit/dashboard/jobs/srpm-builds
  • ...
• /projects/packit/dashboard/pipelines

Categorization in sidebar

For Packit specific pages and external links we should move the to its own category in the sidebar, this would make a good separation between what is an application link and external link, and allows puts usage away from project specific data

Sidebar should then look like

• Projects
  • {context selector} (maybe here or somewhere else)
  • Jobs
  • Pipelines
• Usage
• External links
  • Status
  • Blog posts
  • FAQ

[Venefilyn]

I guess #196 is very similar

[lachmanfrantisek]

@SpyTec Thanks for such a detailed description! A few notes:

• I really like being explicit about external links being external...;)
• I quite like that you can still view all the jobs/pipelines but people can filter that.
• Would it be possible to cover also filtering by the namespace? (That's what people are usually interested.)

[Venefilyn]

Would it be possible to cover also filtering by the namespace? (That's what people are usually interested.)

If we have a list of items that include both, so all options are oamg/convert2rhel, packit/dashboard, I don't see why we can't also include namespaces

[lachmanfrantisek]

Even though we agreed this is important, we didn't pick this as a top Packit team priority for the next quarter and preferred epics with bigger user benefits. (Sadly, we have limited resources.) If anyone (not only @SpyTec ) wants to help us with this, we will be really glad. We are open to any collaboration and have successfully implemented/started multiple affords thanks to people outside of the Packit team.