quality/forge-helpers
8
0
Fork 1
Code Issues Pull requests 2 Projects Releases Packages Wiki Activity Actions

Port all migrated repos to standard priority labels #1

New issue
Closed
opened 2026-01-28 17:34:59 +00:00 by adamwill · 3 comments
adamwill commented 2026-01-28 17:34:59 +00:00
Owner
Copy link

As part of the Pagure migration process, each repo had priority labels created. But we have 'standard' priority labels in Forgejo, created at the instance level and forked for each org as it's created. It would be good to use those labels instead of the per-repo labels created by the migration process, for consistency across the whole of Forge.

I'm writing a script to do this, copying chunks of code from the ones kparal wrote already. It shouldn't be difficult.

As part of the Pagure migration process, each repo had priority labels created. But we have 'standard' priority labels in Forgejo, created at the instance level and forked for each org as it's created. It would be good to use those labels instead of the per-repo labels created by the migration process, for consistency across the whole of Forge. I'm writing a script to do this, copying chunks of code from the ones kparal wrote already. It shouldn't be difficult.
adamwill added this to the Sprint 2 project 2026-01-28 17:34:59 +00:00
adamwill commented 2026-02-07 02:48:44 +00:00
Author
Owner
Copy link

I got the script working yesterday and converted a couple of smaller repos. Will polish it up a bit and run it on the other repos on Monday I guess.

I got the script working yesterday and converted a couple of smaller repos. Will polish it up a bit and run it on the other repos on Monday I guess.
adamwill commented 2026-02-10 02:40:26 +00:00
Author
Owner
Copy link

OK, I've now converted every repo except https://forge.fedoraproject.org/quality/tickets and submitted #3 with the script in it. I figured I'd wait till tomorrow's meeting to see if anyone sees any problems with the already-migrated repos or the script itself, before running it on the quality/tickets repo, since that's the biggest and most important.

OK, I've now converted every repo except https://forge.fedoraproject.org/quality/tickets and submitted https://forge.fedoraproject.org/quality/forge-helpers/pulls/3 with the script in it. I figured I'd wait till tomorrow's meeting to see if anyone sees any problems with the already-migrated repos or the script itself, before running it on the quality/tickets repo, since that's the biggest and most important.
adamwill commented 2026-02-10 21:19:55 +00:00
Author
Owner
Copy link

OK, https://forge.fedoraproject.org/quality/tickets is done now. #3 just needs review by @kparal . Closing this.

OK, https://forge.fedoraproject.org/quality/tickets is done now. https://forge.fedoraproject.org/quality/forge-helpers/pulls/3 just needs review by @kparal . Closing this.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
label-convert
No results found.
Labels
Clear labels
  
Backlog Status
Needs 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 Status
Ready
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.

  
points
01
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.

  
points
02
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.

  
points
03
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.

  
points
05
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.

  
points
08
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.

  
points
13
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.

  
Priority
Critical
This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  
Priority
High
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.

  
Priority
Low
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.

  
Priority
Medium
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 Status
Blocked
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
Sprint Status
Done
Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
Sprint Status
To 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 Item
Bug
Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic
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 Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
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 Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 2
Assignees
Clear assignees
No assignees
adamwill
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
quality/forge-helpers#1
No description provided.