design/tickets
16
4
Fork 1
Code Issues 37 Pull requests Projects 4 Activity

Officially move ticket tracker to Forgejo #8

New issue
Closed
opened 2026-02-23 17:29:11 +00:00 by ekidney · 5 comments
ekidney commented 2026-02-23 17:29:11 +00:00
Owner
Copy link

What do you need?

Once PR#2 is merged and ticket #139 is closed, we can then officially move our ticket tracker to Forgejo. For this, we need to:

  • Turn off the issue tracker on GitLab
  • Make a clear notice on our GitLab as to where to find our new ticket tracker.
  • Update the link on our docs to point to our Forgejo.
  • Update the link on Matrix to point to our Forgejo.
  • Update anywhere else that has the GitLab link listed.

Problem Statement

It will help people know where they can log a design request with us & hopefully ease the confusion.

Contacts

Myself or Madeline

Deadline

Once PR#2 is merged and ticket #139 is closed,

Who will benefit?

Fedora community

Inspiration Examples / Competitive Analysis

I like how clear releng did theirs:

https://pagure.io/releng

although we dont need to be as detailed I think. Here are other examples:

https://gitlab.com/fedora/commops

https://pagure.io/fedora-infrastructure

Priority/Severity

  • High (This will bring a huge increase in performance/productivity/usability cover)
## What do you need? <!-- In your own words, what are you asking the Fedora Design team for help with? !--> Once [PR#2](https://forge.fedoraproject.org/design/tickets/pulls/2) is merged and [ticket #139](https://gitlab.com/fedora/design/team/requests/-/issues/139) is closed, we can then officially move our ticket tracker to Forgejo. For this, we need to: - Turn off the issue tracker on GitLab - Make a clear notice on our GitLab as to where to find our new ticket tracker. - Update the link on our docs to point to our Forgejo. - Update the link on Matrix to point to our Forgejo. - Update anywhere else that has the GitLab link listed. ## Problem Statement <!-- What is the issue being faced that this design request will help? !--> It will help people know where they can log a design request with us & hopefully ease the confusion. ## Contacts <!-- Who is the primary contact to whom the Fedora Design team can speak with about this issue and deliver the output to? Which Fedora team/project/etc. is this request being made for? !--> Myself or Madeline ## Deadline <!-- When do you need this by? If this is for an event, please let us know the date of the event and any lead time you need to get materials produced. !--> <!-- In case you have no specific date we will apply a due date based on your priority: Low - 6 months, Medium - 3 months !--> Once [PR#2](https://forge.fedoraproject.org/design/tickets/pulls/2) is merged and [ticket #139](https://gitlab.com/fedora/design/team/requests/-/issues/139) is closed, ## Who will benefit? <!-- Will this address a need that only one user has, or will it benefit a lot of people? Which people? !--> Fedora community ## Inspiration Examples / Competitive Analysis <!-- Are there any examples of this which exist in other projects? !--> I like how clear releng did theirs: https://pagure.io/releng although we dont need to be as detailed I think. Here are other examples: https://gitlab.com/fedora/commops https://pagure.io/fedora-infrastructure ## Priority/Severity <!-- Delete as appropriate. The priority and severity assigned may be different to this !--> - [ ] High (This will bring a huge increase in performance/productivity/usability cover)
ekidney self-assigned this 2026-02-23 17:29:11 +00:00
ekidney commented 2026-02-26 15:40:19 +00:00
Author
Owner
Copy link

@madelinepeck and I completed the following:

  • Make a clear notice on our GitLab as to where to find our new ticket tracker.
  • Update the link on our docs to point to our Forgejo.
  • Update the link on Matrix to point to our Forgejo.
  • Update anywhere else that has the GitLab link listed.

Will have to wait until all the tickets are closed out on GitLab to turn off issues there completely.

@madelinepeck and I completed the following: - Make a clear notice on our GitLab as to where to find our new ticket tracker. - Update the link on our docs to point to our Forgejo. - Update the link on Matrix to point to our Forgejo. - Update anywhere else that has the GitLab link listed. Will have to wait until all the tickets are closed out on GitLab to turn off issues there completely.
👍 1
niknikovsky commented 2026-03-10 08:29:29 +00:00
Member
Copy link

We could close/move those tickets semi quickly:
https://gitlab.com/fedora/design/team/requests/-/work_items/123
https://gitlab.com/fedora/design/team/requests/-/work_items/78 (maybe, since inactivity)
https://gitlab.com/fedora/design/team/requests/-/work_items/67 (I think it's related to #32)
https://gitlab.com/fedora/design/team/requests/-/work_items/61 (Completed, inactivity)
https://gitlab.com/fedora/design/team/requests/-/work_items/54 (Completed, I think @jflory7's opinion was requested)
https://gitlab.com/fedora/design/team/requests/-/work_items/21 (Bit of a dispute, but no one seems to work on this)
https://gitlab.com/fedora/design/team/requests/-/work_items/113 (Move to Forge?)
Which I think would just leave us with #121 and #116

We could close/move those tickets semi quickly: https://gitlab.com/fedora/design/team/requests/-/work_items/123 https://gitlab.com/fedora/design/team/requests/-/work_items/78 (maybe, since inactivity) https://gitlab.com/fedora/design/team/requests/-/work_items/67 (I think it's related to #32) https://gitlab.com/fedora/design/team/requests/-/work_items/61 (Completed, inactivity) https://gitlab.com/fedora/design/team/requests/-/work_items/54 (Completed, I think @jflory7's opinion was requested) https://gitlab.com/fedora/design/team/requests/-/work_items/21 (Bit of a dispute, but no one seems to work on this) https://gitlab.com/fedora/design/team/requests/-/work_items/113 (Move to Forge?) Which I think would just leave us with [#121](https://gitlab.com/fedora/design/team/requests/-/work_items/121) and [#116](https://gitlab.com/fedora/design/team/requests/-/work_items/116)
ekidney commented 2026-03-10 09:28:47 +00:00
Author
Owner
Copy link

@niknikovsky I think this comment is more suited for #5 - so I'll have a look and comment over there! Thanks

@niknikovsky I think this comment is more suited for https://forge.fedoraproject.org/design/tickets/issues/5 - so I'll have a look and comment over there! Thanks
👍 1
niknikovsky commented 2026-03-10 09:37:06 +00:00
Member
Copy link

Copied the comment there.

Copied the comment there.
ekidney commented 2026-03-12 09:29:02 +00:00
Author
Owner
Copy link

The Gitlab has been archived! It is still accessible in rad-only mode here: https://gitlab.com/groups/fedora/design/team/-/inactive

and old tickets can be viewed here in read-only mode too: https://gitlab.com/fedora/design/team/requests/-/work_items

Closing as complete :)

The Gitlab has been archived! It is still accessible in rad-only mode here: https://gitlab.com/groups/fedora/design/team/-/inactive and old tickets can be viewed here in read-only mode too: https://gitlab.com/fedora/design/team/requests/-/work_items Closing as complete :)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
Acceptance
Fedora Design
This is a valid ticket that should be addressed and has been accepted by the Fedora Design Team

  
Acceptance
Needs Info
This ticket needs additional info in order for us to triage it.

  
Acceptance
Wont fix
Ticke is rejected for various reasons: budget approval needed, mindshare approval needed, duplicate / already completed, already part of a larger-scoped plan, redirected to another team, no resources.

  
Design Docs Revamp

Revamping the Design Docs with new updated info and moving from the wiki to docs site.

  
Engagement
Long-term
Ticket that might require weeks to months to work on.

  
Engagement
Medium-term
Ticket that might take days to weeks to engage on.

  
Engagement
Short-term
Ticket that might require hours to days to work on.

  
F45 Wallpaper

All tickets correlated to F45 wallpaper process

  
needs review

Ticket needs to be reviewed and triaged by the Fedora Design Team.

  
Newbie
Needs research
A ticket that someone new to the team could complete, but will require them to get some help/background.

  
Newbie
Well-documented
A ticket that someone new to the team could complete and is well-documented.

  
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
High
This is for work that is critical and needs to be addressed next sprint. It's often for tickets that are time-sensitive, align to Fedora Strategic Initiatives, or is a leadership request.

  
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.

  
Status
Backlog
Items that have been triaged and that we aren't actively working on.

  
Status
In Progress
Items being actively worked on.

  
Status
In Review
Ticket is awaiting review by a team member or the requester.

  
Type
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.

  
Type
Request
A ticket related to an incoming external request (not filed by a designer.)

  
Type
Sub Epic
A smaller segment of work that falls under a larger epic, helping designers break down complex tasks into more manageable parts.

No labels
Acceptance
Fedora Design
Acceptance
Needs Info
Acceptance
Wont fix
Design Docs Revamp
Engagement
Long-term
Engagement
Medium-term
Engagement
Short-term
F45 Wallpaper
needs review
Newbie
Needs research
Newbie
Well-documented
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Status
Backlog
Status
In Progress
Status
In Review
Type
Epic
Type
Request
Type
Sub Epic
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 2026-03-09 to 2026-03-23
Assignees
Clear assignees
No assignees
ekidney
madelinepeck
2 participants
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
design/tickets#8
No description provided.