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

Implement user/namespace/project usage metrics #1990

Open
Tracked by #2108
lachmanfrantisek opened this issue Apr 4, 2023 · 1 comment
Open
Tracked by #2108

Implement user/namespace/project usage metrics #1990

lachmanfrantisek opened this issue Apr 4, 2023 · 1 comment
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@lachmanfrantisek
Copy link
Member

lachmanfrantisek commented Apr 4, 2023 •
edited by lbarcziova
Loading

@lachmanfrantisek lachmanfrantisek mentioned this issue Apr 4, 2023
Closed
3 tasks
@lachmanfrantisek lachmanfrantisek changed the title Implement action limits Implement user/namespace/project limits Apr 4, 2023
@majamassarini majamassarini moved this from new to backlog in Packit Kanban Board Apr 6, 2023
@lachmanfrantisek lachmanfrantisek mentioned this issue Apr 10, 2023
Open
6 tasks
@lachmanfrantisek lachmanfrantisek moved this from backlog to ready-to-refine in Packit Kanban Board Apr 19, 2023
@lachmanfrantisek lachmanfrantisek moved this from ready-to-refine to backlog in Packit Kanban Board Apr 19, 2023
@lachmanfrantisek lachmanfrantisek moved this from backlog to ready-to-refine in Packit Kanban Board May 10, 2023
@lachmanfrantisek lachmanfrantisek added complexity/single-task Regular task, should be done within days. impact/high This issue impacts multiple/lot of users. area/general Related to whole service, not a specific part/integration. gain/high This brings a lot of value to (not strictly a lot of) users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels May 10, 2023
@mfocko mfocko moved this from ready-to-refine to refined in Packit Kanban Board May 11, 2023
@lbarcziova lbarcziova mentioned this issue May 11, 2023
Open
@lbarcziova lbarcziova changed the title Implement user/namespace/project limits Implement user/namespace/project usage metrics May 11, 2023
@lbarcziova lbarcziova mentioned this issue Jun 29, 2023
Open
2 tasks
@majamassarini majamassarini moved this from refined to backlog in Packit Kanban Board Jun 29, 2023
@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
@lbarcziova
Copy link
Member

This is still relevant, let's revisit once we start hitting issues with resources more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/high This issue impacts multiple/lot of users. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lachmanfrantisek @lbarcziova