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.

Sign up for GitHub

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

Jump to bottom

Show package name for pull-from-upstream and propose-downstream #358

Open
lbarcziova opened this issue Nov 15, 2023 · 0 comments
Open

Show package name for pull-from-upstream and propose-downstream #358

lbarcziova opened this issue Nov 15, 2023 · 0 comments
Labels
area/fedora Related to Fedora ecosystem 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/low This issue impacts only a few users. kind/feature New feature or a request for enhancement.

Comments

@lbarcziova
Copy link
Member

We show only the trigger of these jobs and not the actual package that is being updated and I am quite missing this information.

This will probably also require changes in packit-service API (and DB?) as I do not see this information exposed via API currently.
@lbarcziova lbarcziova added kind/feature New feature or a request for enhancement. area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. labels Nov 15, 2023
@lachmanfrantisek lachmanfrantisek added gain/low This doesn't bring that much value to users. impact/low This issue impacts only a few users. area/user-experience Usability issue labels Nov 16, 2023
@lachmanfrantisek lachmanfrantisek moved this from new to backlog in Packit Kanban Board Nov 16, 2023
lbarcziova added a commit to lbarcziova/dashboard that referenced this issue Feb 26, 2024
@lbarcziova
Link package in relese sync results
d9a9640 
Partially fixes packit#358 (for failed syncs, the info is still
missing).
lbarcziova added a commit to lbarcziova/dashboard that referenced this issue Mar 4, 2024
@lbarcziova
Link package in relese sync results
6a69ee3 
Partially fixes packit#358 (for failed syncs, the info is still
missing).
github-merge-queue bot pushed a commit that referenced this issue Mar 4, 2024
@lbarcziova
Link package in relese sync results
35102c3 
Partially fixes #358 (for failed syncs, the info is still
missing).
github-merge-queue bot pushed a commit that referenced this issue Mar 4, 2024
@lbarcziova
Link package in relese sync results
7e44881 
Partially fixes #358 (for failed syncs, the info is still
missing).
github-merge-queue bot pushed a commit that referenced this issue Mar 4, 2024
@lbarcziova
Link package in relese sync results
f24aea7 
Partially fixes #358 (for failed syncs, the info is still
missing).
github-merge-queue bot pushed a commit that referenced this issue Mar 5, 2024
@lbarcziova
Link package in relese sync results
6fbef60 
Partially fixes #358 (for failed syncs, the info is still
missing).
github-merge-queue bot pushed a commit that referenced this issue Mar 5, 2024
@lbarcziova
Link package in relese sync results
92d04ad 
Partially fixes #358 (for failed syncs, the info is still
missing).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/fedora Related to Fedora ecosystem 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/low This issue impacts only a few users. kind/feature New feature or a request for enhancement.
Projects
Packit Kanban Board
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lachmanfrantisek @lbarcziova