67 labels
-
announcementArchived
-
anubis
Issues related to anubis -
authentication
Authentication related issues -
aws
Issues related to Amazon Web Services -
backlog
Tasks that will take longer then ~4 hours to doArchived -
blocked
Issue is blockedArchived -
bodhi
Issues with Bodhi -
ci
Continuous Integration -
cloud
Items in FedoraInfraCloud or COmmunishift -
communishift
issues/questions about os.edorainfracloud.org ( Community OpenShift) -
copr
COPR system (run by other team) -
database
Issues related to databases -
day-to-day
These are small self contained tasks that are part of normal operations, but are async from sprint planning. -
dc-move
Items related to datacenter moveArchived -
deprecated
Tools which Infrastructure may not be able to fixArchived -
dev
Tasks requiring some dev work -
discourse
outsourced tool -
dns
Changes or problems with DNS -
downloads
rsync,dl.fp.o,AWS,torrents -
easyfixArchived
-
epel
Issues relating to epelArchived -
firmitas
-
forgejo_migration
Request migration to the new forge -
GainHigh
task that gets us a lot / is important / makes many people happyArchived -
GainLow
tasks that gets us little / isn't very important / makes only 1 person or few happyArchived -
GainMedium
task that gets us some / is somewhat important / makes some people happyArchived -
gitlab
-
greenwave
Issues with greenwave -
hardware
Problem is with Fedora Infrastructure Owned/Leased Hardware -
help wanted
-
high-trouble
task that is complex/long/difficultArchived -
koji
Issues with the build system -
koschei
Items needing Koschei team -
lists
issues with lists -
low-trouble
task that is easy/shortArchived -
medium-trouble
task that is medium complex / difficultArchived -
mirrorlists
Way to tell systems where downloads are -
monitoring
-
Needs investigation
-
odcs
On Demand Compose Service issuesArchived -
OpenShift
Issues with OpenShift -
ops
ops problem now...Archived -
outage
-
packager_workflow_blocker
Blocks the packager workflowArchived -
pagure
Issues with pagure.io -
permissions
Items which need permissions set in outside tools -
PriorityNeeds Review
Priority of Needs ReviewArchived -
PriorityNext Meeting
Priority of Next MeetingArchived -
Priority🔥 URGENT 🔥
Priority of 🔥 URGENT 🔥Archived -
PriorityWaiting on Assignee
Priority of Waiting on AssigneeArchived -
PriorityWaiting on External
Priority of Waiting on ExternalArchived -
PriorityWaiting on Reporter
Priority of Waiting on ReporterArchived -
rabbitmq
issues with the message broker -
release-monitoring
release-monitoring.org (Anitya) -
releng
For problems which should be in the releng ticket systemArchived -
request-for-resources
-
s390x
The secondary architecture hardware and problems related with it -
security
-
SMTP
Email issues outside of lists (DMARC, SPF, aliases) -
sprint-0Archived
-
sprint-1Archived
-
src.fp.o
Issues related to src.fedoraproject.org -
staging
Issues in staging -
unfreeze
Patches to be applied after freeze is lifted -
waiverdb
Issues with waiverdb -
websites-general
General items with a website focus -
wiki
Issues with the Wiki -
Organization level labels that can be used with all repositories under this organization
-
Backlog StatusNeeds Review
Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning. -
Backlog StatusReady
Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available. -
chore
Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean. -
documentation
Work focused on creating, updating, or improving documentation for users, developers, or system administrators. -
points01
A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research. -
points02
This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty. -
points03
Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change. -
points05
A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams. -
points08
Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete. -
points13
Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down. -
PriorityHigh
This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work. -
PriorityLow
This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period. -
PriorityMedium
This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints. -
Sprint StatusBlocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution. -
Sprint StatusDone
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint. -
Sprint StatusIn Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening. -
Sprint StatusReview
Work items that are complete but need review, testing, or approval before being marked as done. -
Sprint StatusTo Do
Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members. -
Technical Debt
Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features. -
Work ItemBug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior. -
Work ItemEpic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints. -
Work ItemSpike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions. -
Work ItemTask
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value. -
Work ItemUser Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.