Aggregated views

[TomasTomecek]

This is an epic where we'd provide views for

• project
• release
• PR
• commit

we already have something but it's hard to navigate the output

the point of this epic is

• to make information in those views easy to navigate
• provide human-readable information (PR titles, commit sha & title, sorted by activity)
• for PRs, provide history of all runs

related: #130

Q1 2023 planning outcome:

• We find this epic to be beneficial that everyone would spend less time looking for the right information once this is implemented
• It would make our frontend more pleasant to use: less time and clicks to find the right the data

[bocekm]

Details on the point that "it's hard to navigate the output":

1. https://dashboard.packit.dev/projects/

I need to fill in all three boxes (forge, namespace, repo name). I'd be great if I can filter the repos by typing into any one of the three boxes.

2. https://dashboard.packit.dev/projects/github.com/oamg/convert2rhel

The "PRs Handled" prints the latest 10 PRs. If I want information on an old PR, let's say #300 when the latest is #686, I need to click the "Load More" button many many times. I propose adding a box for filtering the listed PRs.

3. https://dashboard.packit.dev/projects/github.com/oamg/convert2rhel

Clicking the "Load More" button I mention above has no feedback on whether it is doing something after clicking. Currently nothing happens after clicking it for ~10 seconds and then another 10 PRs are loaded. I propose adding some kind of spinning wheel to indicate that more PRs are being loaded.

4. https://dashboard.packit.dev/projects/github.com/oamg/convert2rhel

The listed test runs under a PR provide no information when they were executed or what git commit they were run for. If the test suite is executed 2+ times on a PR, then I have no way of knowing what's the last test executed. I propose adding at least a timestamp and sort the listed test entries based on the timestamp.

[Venefilyn]

As far as this is concerned we need to implement a search within the server itself that we can query instead of having to input everything ourselves. @TomasTomecek do we have an issue created for this in the packit repo? I know I added one for filtering but don't think I created one for the searching. Once that is up I should be able to tackle this one fairly easily

[TomasTomecek]

@SpyTec not aware of one for searching: maybe we could combine that into one request: one endpoint that can both search and filter (to me, they sound like the same thing)

[lbarcziova]

In the brainstorming session earlier this month we agreed on several changes for /projects view:

• be able to filter projects easily:
  • for upstream-related pipelines: Upstream repository -> PR/branch/release tag + commit hash
  • for downstream release-related pipelines: Dist-git repo -> commit hash + branch
• show pipelines directly (instead of the current content)

This will firstly require having more efficient DB and API (ideally pipeline-centric): related to packit/packit-service#1848.

[lachmanfrantisek]

After a team discussion, 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.