Move over open / not worked on GitLab issues to Forgejo #5

Closed
opened 2026-02-17 16:26:10 +00:00 by ekidney · 12 comments
Owner

Design Request

What do you need?

We have a number of open tickets on GitLab that haven't been worked on yet and won't be complete by the time we want to be fully migrated to Forgejo. We need to manually bring them over here. This can be done by copy and pasting the description, linking the original ticket and the person who logged it.

I want to specify that we are bringing over tickets that have not been worked on yet. Any tickets that are actively being worked on over on GitLab can stay there. We can bring over any completed assets created on them and store them in the relevant folder here on Forgejo.

Once the issue is opened here, it can be closed on Gitlab with a comment pointing to a link to it here.

Here's an example of an issue on GitLab:

image1

And then it brought over to Forgejo:

image2

and then the issue can be closed on GitLab with a link to the ticket here:

image3

Problem Statement

We have open tickets on Gitlab but if we want to start working from this repo exclusively we will need all the open tickets brought over.

Contacts

Me :)

Deadline

We would like this to be done asap but we can work away on it as we have time.

Who will benefit?

The Fedora Design Team

Priority/Severity

  • High (This will bring a huge increase in performance/productivity/usability cover)
# Design Request ## What do you need? We have a number of open tickets on GitLab that haven't been worked on yet and won't be complete by the time we want to be fully migrated to Forgejo. We need to manually bring them over here. This can be done by copy and pasting the description, linking the original ticket and the person who logged it. I want to specify that we are bringing over tickets that **have not** been worked on yet. Any tickets that are actively being worked on over on GitLab can stay there. We can bring over any completed assets created on them and store them in the relevant folder here on Forgejo. Once the issue is opened here, it can be closed on Gitlab with a comment pointing to a link to it here. Here's an example of an issue on GitLab: ![image1](/attachments/762b19f3-15cd-4695-beb9-d09450511565) And then it brought over to Forgejo: ![image2](/attachments/9053ada8-d395-4252-bf25-103a1c03b42d) and then the issue can be closed on GitLab with a link to the ticket here: ![image3](/attachments/687031ee-f7eb-44bd-9910-98b5fc6701e5) ## Problem Statement <!-- What is the issue being faced that this design request will help? !--> We have open tickets on Gitlab but if we want to start working from this repo exclusively we will need all the open tickets brought over. ## 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? !--> Me :) ## 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. !--> We would like this to be done asap but we can work away on it as we have time. ## Who will benefit? <!-- Will this address a need that only one user has, or will it benefit a lot of people? Which people? !--> The Fedora Design Team ## 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 16:54:17 +00:00
Member

All of the images are not found..

All of the images are not found..
Member

And I also do not have access to add any labels

And I also do not have access to add any labels
Author
Owner

@niknikovsky Images should be working now. I added you to the design-team FAS so you should be able to add labels once that syncs up here. You may need to log out and in again.

@niknikovsky Images should be working now. I added you to the design-team FAS so you should be able to add labels once that syncs up here. You may need to log out and in again.
Member

@ekidney wrote in #5 (comment):

@niknikovsky Images should be working now. I added you to the design-team FAS so you should be able to add labels once that syncs up here. You may need to log out and in again.

Images work, I've signed out and in and I still can't add labels.
Maybe it's a role issue in the Forge design group?

@ekidney wrote in https://forge.fedoraproject.org/design/tickets/issues/5#issuecomment-544397: > @niknikovsky Images should be working now. I added you to the design-team FAS so you should be able to add labels once that syncs up here. You may need to log out and in again. Images work, I've signed out and in and I still can't add labels. Maybe it's a role issue in the Forge design group?
Author
Owner

@niknikovsky I changed the permissions, can you let me know if it works now?

@niknikovsky I changed the permissions, can you let me know if it works now?
Member

@ekidney, yes it works now

@ekidney, yes it works now
Member

As @ekidney requested, I'm moving the comment here:

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

As @ekidney requested, I'm moving the comment here: > 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)
Author
Owner

@niknikovsky wrote in #5 (comment):

As @ekidney requested, I'm moving the comment here:

We could close/move those tickets semi quickly:
https://gitlab.com/fedora/design/team/requests/-/work_items/123

This can be migrated over. When closing, leave a comment advising the work will be continued on the Forgejo ticket. On the Forgejo ticket mention that there was previous work and comments on GitLab.

https://gitlab.com/fedora/design/team/requests/-/work_items/78 (maybe, since inactivity)

This can be closed. I would leave a comment advising to log a new ticket on our Forgejo if more help or feedback is needed in the future and I would paste a link to our ticket tracker.

https://gitlab.com/fedora/design/team/requests/-/work_items/67 (I think it's related to #32)

This can be migrated over.

https://gitlab.com/fedora/design/team/requests/-/work_items/61 (Completed, inactivity)

This can be closed as complete. I uploaded the files from this ticket here: https://forge.fedoraproject.org/design/design-assets/src/branch/main/misc/business-cards

https://gitlab.com/fedora/design/team/requests/-/work_items/54 (Completed, I think @jflory7's opinion was requested)

This can be closed! I think they did a great job with the page design. I would leave a comment advising to log a new ticket on our Forgejo if more help or feedback is needed in the future and I would paste a link to our ticket tracker.

https://gitlab.com/fedora/design/team/requests/-/work_items/21 (Bit of a dispute, but no one seems to work on this)

I would migrate this over and leave a comment on the Gitlab issue advising the work will be continued on the Forgejo ticket.

https://gitlab.com/fedora/design/team/requests/-/work_items/113 (Move to Forge?)

This can be migrated over too. When closing, leave a comment advising the work will be continued on the Forgejo ticket. On the Forgejo ticket mention that there was previous work and comments on GitLab. I would also comment or link Madelines design file on the new Forgejo ticket.

Which I think would just leave us with #121 and #116

We can bring these over to Foregjo too - we can leave a comment advising the work will be continued on the Forgejo ticket & on the Forgejo ticket mention that there was previous work and comments on GitLab. We can bring over the latest piece of feedback and design file for each one in a comment. The Gitlab will be archived so everything will be in read-only mode, so we can still view the history on the tickets. But since you're the one working on these tickets, what would you prefer? We can keep them on GitLab until complete if it's easier for you and then archive the GitLab afterwards.

@niknikovsky wrote in https://forge.fedoraproject.org/design/tickets/issues/5#issuecomment-576992: > As @ekidney requested, I'm moving the comment here: > > We could close/move those tickets semi quickly: > https://gitlab.com/fedora/design/team/requests/-/work_items/123 This can be migrated over. When closing, leave a comment advising the work will be continued on the Forgejo ticket. On the Forgejo ticket mention that there was previous work and comments on GitLab. > https://gitlab.com/fedora/design/team/requests/-/work_items/78 (maybe, since inactivity) This can be closed. I would leave a comment advising to log a new ticket on our Forgejo if more help or feedback is needed in the future and I would paste a link to our ticket tracker. > https://gitlab.com/fedora/design/team/requests/-/work_items/67 (I think it's related to #32) This can be migrated over. > https://gitlab.com/fedora/design/team/requests/-/work_items/61 (Completed, inactivity) This can be closed as complete. I uploaded the files from this ticket here: https://forge.fedoraproject.org/design/design-assets/src/branch/main/misc/business-cards > https://gitlab.com/fedora/design/team/requests/-/work_items/54 (Completed, I think @jflory7's opinion was requested) This can be closed! I think they did a great job with the page design. I would leave a comment advising to log a new ticket on our Forgejo if more help or feedback is needed in the future and I would paste a link to our ticket tracker. > https://gitlab.com/fedora/design/team/requests/-/work_items/21 (Bit of a dispute, but no one seems to work on this) I would migrate this over and leave a comment on the Gitlab issue advising the work will be continued on the Forgejo ticket. > https://gitlab.com/fedora/design/team/requests/-/work_items/113 (Move to Forge?) This can be migrated over too. When closing, leave a comment advising the work will be continued on the Forgejo ticket. On the Forgejo ticket mention that there was previous work and comments on GitLab. I would also comment or link Madelines design file on the new Forgejo ticket. > 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) We can bring these over to Foregjo too - we can leave a comment advising the work will be continued on the Forgejo ticket & on the Forgejo ticket mention that there was previous work and comments on GitLab. We can bring over the latest piece of feedback and design file for each one in a comment. The Gitlab will be archived so everything will be in read-only mode, so we can still view the history on the tickets. But since you're the one working on these tickets, what would you prefer? We can keep them on GitLab until complete if it's easier for you and then archive the GitLab afterwards.
Member

I personally believe that having to open both GitLab and Forge might be a bit confusing and do not know why the comment did not send earlier, I'll also have checkmarks mostly for myself, but anyone else feel free to edit this

  • Migrate 123 to Forge
  • Close 78
  • Migrate over ticket 67
  • Close 61
  • Close 54
  • Migrate 21
  • Migrate 113
  • Migrate 121
  • Migrate 116
I personally believe that having to open both GitLab and Forge might be a bit confusing and do not know why the comment did not send earlier, I'll also have checkmarks mostly for myself, but anyone else feel free to edit this - [x] Migrate 123 to Forge - [x] Close 78 - [x] Migrate over ticket 67 - [x] Close 61 - [x] Close 54 - [x] Migrate 21 - [x] Migrate 113 - [x] Migrate 121 - [x] Migrate 116
Member

This only leaves this ticket open, which was updated semi recently, so I will leave that up to you

This only leaves [this](https://gitlab.com/fedora/design/team/requests/-/work_items/44) ticket open, which was updated semi recently, so I will leave that up to you
Member

It has been closed with guidance from Matthew which means we can now shut down the GitLab.

It has been closed with guidance from [Matthew](https://matrix.to/#/!XrTxTdgakZPaJuUzbH:matrix.org/$lK0rN8Lr9AboGpTcpTGeg0_dawQAkaPh0WZlESC-XYU?via=fedora.im&via=matrix.org&via=gnome.org) which means we can now shut down the GitLab.
Author
Owner

Thank you for your work on this @niknikovsky! Closing this out as complete :)

Thank you for your work on this @niknikovsky! Closing this out as complete :)
Sign in to join this conversation.
No milestone
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#5
No description provided.