# Swift Bugs have migrated to GitHub Issues! **URL:** \ **Category:** Announcements\ **Created:** [April 25, 2022, 4:04pm UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960 "2022-04-25T16:04:53Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![mishal\_shah](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mishal_shah/32/247_2.png) [@mishal\_shah](https://forums.swift.org/u/mishal_shah)\ **Post date:** [April 25, 2022, 4:04pm UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/1 "2022-04-25T16:04:53Z")
Happy to announce Swift Bugs have migrated to [GitHub Issues](https://github.com/apple/swift/issues)! In this first phase, all of the issues are "cloned" into the apple/swift repository. Next, we are working on transferring GitHub Issues to corresponding GitHub repositories. More detail about the [migration process](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125). Thank you to everyone who helped! ---
**Author:** ![kiel](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/kiel/32/1392_2.png) [@kiel](https://forums.swift.org/u/kiel)\ **Post date:** [April 26, 2022, 2:58am UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/2 "2022-04-26T02:58:40Z")
Goodness me, that GitHub UI is a breath of fresh air compared to the Jira one. It鈥檚 vastly easier for me to find other ways I can be involved. Thank you! ---
**Author:** ![Karl](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@Karl](https://forums.swift.org/u/Karl)\ **Post date:** [April 26, 2022, 1:17pm UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/3 "2022-04-26T13:17:53Z")
Just being able to read a bug report without logging in is so good 馃槶 ---
**Author:** ![Mordil](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mordil/32/5840_2.png) [@Mordil](https://forums.swift.org/u/Mordil)\ **Post date:** [April 26, 2022, 2:54pm UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/4 "2022-04-26T14:54:51Z")
Well, to a separate account and system that is 馃槒 ---
**Author:** ![Jon\_Shier](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jon_shier/32/921_2.png) [@Jon\_Shier](https://forums.swift.org/u/Jon_Shier)\ **Post date:** [April 28, 2022, 1:16am UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/5 "2022-04-28T01:16:18Z")
It looks like some issues were imported and then immediately closed. Does that mean they were closed on Jira and the reason wasn't imported, or did something happen during the import process. For example, [[SR-16123] Non-escaping closure capturing `inout` wrongly assessed as escaping =\> error 路 Issue #58382 路 apple/swift 路 GitHub](https://github.com/apple/swift/issues/58382) ---
**Author:** ![blangmuir](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/blangmuir/32/277_2.png) [@blangmuir](https://forums.swift.org/u/blangmuir)\ **Post date:** [April 28, 2022, 3:23am UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/6 "2022-04-28T03:23:57Z")
That issue was marked resolved on JIRA before the migration, although in that specific case it looks like it may have been a mistake and I asked the originator if it should be reopened. ---
**Author:** ![SDGGiesbrecht](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/sdggiesbrecht/32/4768_2.png) [@SDGGiesbrecht](https://forums.swift.org/u/SDGGiesbrecht)\ **Post date:** [April 29, 2022, 11:47pm UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/7 "2022-04-29T23:47:31Z")
They are much easier to search now. 馃帀 I quickly discovered some I had forgotten about that can be closed now. The timeline slated the migration to be complete and be fully usable by yesterday, but the button to close an issue is still missing. Was the migration delayed and ongoing, or is there a permissions problem? This is an example: [https://github.com/apple/swift/issues/57611](https://github.com/apple/swift/issues/57611). I appear to have the option to comment, but not to close it. ![Bildschirmfoto 2022-04-29 um 17.47.01](https://global.discourse-cdn.com/swift/original/3X/9/4/94fb8d18f547e2d890caadddb30f40c74fd726b4.png) ---
**Author:** ![benrimmington](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/benrimmington/32/695_2.png) [@benrimmington](https://forums.swift.org/u/benrimmington)\ **Post date:** [April 30, 2022, 2:58am UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/8 "2022-04-30T02:58:55Z")
> [@SDGGiesbrecht](#): > > This is an example: [https://github.com/apple/swift/issues/57611](https://github.com/apple/swift/issues/57611). I appear to have the option to comment, but not to close it. Did you provide your username mapping, as requested in the previous announcement? > [@Swift bugs are moving to GitHub Issues and we need your help!](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/1): > > JIRA issues whose creator does not appear in the mapping will be cloned to GitHub with a bot account as the creator of the new issue. Once created, it is impossible to change the creator of the new issue in GitHub. Issues and pull requests should be closable by either the original author, or anyone with write access to the repository. - Could your issue be closed as a duplicate of [apple/swift#58058](https://github.com/apple/swift/issues/58058)? - It should probably also be labelled as a Foundation bug, so that it can be moved to the swift-corelibs-foundation repository. ---
**Author:** ![SDGGiesbrecht](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/sdggiesbrecht/32/4768_2.png) [@SDGGiesbrecht](https://forums.swift.org/u/SDGGiesbrecht)\ **Post date:** [April 30, 2022, 5:42am UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/9 "2022-04-30T05:42:25Z")
> [@benrimmington](#): > > Did you provide your username mapping, as requested in the previous announcement? Of course not. Didn鈥檛 seem worth my time with no one paying me to do it. 馃槈 > [@benrimmington](#): > > Issues and pull requests should be closable by either the original author, or anyone with write access to the repository. Makes sense. Since the original author is now a bot, I will just leave comments for whomever comes across it next with write access. (Actually, I am kind of glad they did not get merged with my GitHub user and suddenly overwhelm all my to鈥恉o filters.) ---
**Author:** ![ole](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ole/32/18720_2.png) [@ole](https://forums.swift.org/u/ole)\ **Post date:** [May 19, 2022, 3:17pm UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/10 "2022-05-19T15:17:08Z")
When you open a link to a [bugs.swift.org](http://bugs.swift.org) issue, such as [https://bugs.swift.org/browse/SR-15873](https://bugs.swift.org/browse/SR-15873), you are now greeted with a login screen: ![Screen Shot 2022-05-19 at 17.07.11](https://global.discourse-cdn.com/swift/original/3X/5/1/51e41ef4d721bfa6c33887698a7a67d4590b7195.png) Is this intentional? There's a generic link to the GitHub repo, but not to the concrete issue on GitHub (which is [[SR-15873] Documentation for withUnsafeCurrentTask refers to non-existent property UnsafeCurrentTask.task 路 Issue #58138 路 apple/swift 路 GitHub](https://github.com/apple/swift/issues/58138) in this case). I understand that the plan is to transfer the issues on GitHub to the repositories they "belong" to, but the current user experience is really bad, considering there are now thousands of broken links on the web. @mishal_shah Do you have a timeframe for [the planned redirect from bugs.swift.org URLs to GitHub](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125)? > In the future, we plan to redirect [bugs.swift.org](http://bugs.swift.org/) URLs to the corresponding GitHub Issues. Thanks! ---
**Author:** ![mishal\_shah](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mishal_shah/32/247_2.png) [@mishal\_shah](https://forums.swift.org/u/mishal_shah)\ **Post date:** [May 19, 2022, 4:51pm UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/11 "2022-05-19T16:51:48Z")
> [@ole](#): > > @mishal_shah Do you have a timeframe for [the planned redirect from bugs.swift.org URLs to GitHub](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125)? Redirect for [bugs.swift.org](http://bugs.swift.org) will be available in next few weeks. ---
**Author:** ![masters3d](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@masters3d](https://forums.swift.org/u/masters3d)\ **Post date:** [May 19, 2022, 5:34pm UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/12 "2022-05-19T17:34:57Z")
in the mean time the current [bugs.swift.org](http://bugs.swift.org) link in the title could point to a github search which usually should resolve to only one result `https://github.com/search?q=org%3Aapple+SR-15873&type=issues` ![image](https://global.discourse-cdn.com/swift/original/3X/7/3/73c4eb778a669a3a9f76c097131a5c1783c270d8.png) ---
**Author:** ![mishal\_shah](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mishal_shah/32/247_2.png) [@mishal\_shah](https://forums.swift.org/u/mishal_shah)\ **Post date:** [May 25, 2022, 12:35am UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/13 "2022-05-25T00:35:23Z")
The last phase is now completed: - GitHub Issues transferred to corresponding repositories. - [bugs.swift.org](http://bugs.swift.org) URLs will now redirect to GitHub issues. ---
**Author:** ![ole](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ole/32/18720_2.png) [@ole](https://forums.swift.org/u/ole)\ **Post date:** [May 25, 2022, 9:16am UTC](https://forums.swift.org/t/swift-bugs-have-migrated-to-github-issues/56960/14 "2022-05-25T09:16:09Z")
That's fantastic. Thank you @mishal_shah!