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

TF runs with the same trigger #265

Open
mfocko opened this issue May 25, 2023 · 1 comment
Open

TF runs with the same trigger #265

mfocko opened this issue May 25, 2023 · 1 comment
Labels
area/user-experience Usability issue complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/high This issue impacts multiple/lot of users. kind/bug Something isn't working.

Comments

@mfocko
Copy link
Member

mfocko commented May 25, 2023

When listing the Testing Farm runs, as a user I would expect them to be grouped if they have the same trigger, i.e. set of tests triggered by multiple targets from a Copr build.

example

Example of a similar situation handled by Copr builds:
Copr builds example

@mfocko mfocko added kind/bug Something isn't working. area/user-experience Usability issue complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/high This issue impacts multiple/lot of users. labels May 25, 2023
@lbarcziova lbarcziova added the workshop-ready Ready to be worked on during the workshop at DevConf.CZ 2023 label May 29, 2023
@lbarcziova lbarcziova moved this from new to backlog in Packit Kanban Board May 29, 2023
@lbarcziova lbarcziova removed the workshop-ready Ready to be worked on during the workshop at DevConf.CZ 2023 label Jun 13, 2023
@jpopelka
Copy link
Member

Instead of Status label here use an array of status labels similar to this.
We also need to remove the rightmost Test Results column because it’s different for each target.

@lachmanfrantisek lachmanfrantisek moved this from backlog to priority-backlog in Packit Kanban Board Jan 25, 2024
@lachmanfrantisek lachmanfrantisek moved this from priority-backlog to backlog in Packit Kanban Board Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/user-experience Usability issue complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/high This issue impacts multiple/lot of users. kind/bug Something isn't working.
Projects
Status: backlog
Development

No branches or pull requests

3 participants