# Swift bugs are moving to GitHub Issues and we need your help! **URL:** \ **Category:** Announcements\ **Created:** [March 21, 2022, 11:44pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125 "2022-03-21T23:44:03Z")\ **Posts on this page:** 20\ **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:** [March 21, 2022, 11:44pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/1 "2022-03-21T23:44:03Z")
# Swift bugs are moving to GitHub Issues and we need your help! Swift's open source project issues are currently in JIRA, making it difficult for developers to discover and integrate them into our workflows on GitHub, such as pull requests. To provide a better workflow for developers, we are working on migrating JIRA to GitHub Issues. The issues in JIRA cover multiple repositories for the Swift project in GitHub. We will move issues from JIRA to GitHub using a two-phased process: - Each JIRA issue will be "cloned" to a new GitHub issue in the apple/swift repository. - The newly created GitHub issues will transfer to the GitHub repositories that correspond to the original components in JIRA. Afterward, the JIRA instance will no longer accept the creation of new reports. In the future, we plan to redirect [bugs.swift.org](http://bugs.swift.org) URLs to the corresponding GitHub Issues. We desire each GitHub issue to capture who created the original issue in JIRA faithfully. A username map created by the community will facilitate this mapping. Please follow the steps below to populate this mapping accurately. 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. Thus, we strongly encourage those with filed issues to get the mapping as accurate as possible. ## Actions required - Update Github and JIRA ([bugs.swift.org](http://bugs.swift.org)) username mapping on [forums.swift.org](https://forums.swift.org/my/preferences/profile) by **April 7th 2022** - Go to profile preferences - [Swift Forums](https://forums.swift.org/my/preferences/profile) - Update `JIRA Username` and `GitHub Username` - Accept the invitation to “swift-issues-migration” organization on GitHub by **April 18th 2022** - The invitation will be sent by April 7th 2022 ## Timeline - New users should contact [@swift-infrastructure](https://forums.swift.org/groups/swift-infrastructure) before creating an account starting today on [bugs.swift.org](http://bugs.swift.org) - Update GitHub and [bugs.swift.org](http://bugs.swift.org) username by April 7th 2022 - Accept the invitation to “swift-issues-migration” organization on GitHub by April 18th 2022 - [bugs.swift.org](http://bugs.swift.org) will be in read-only mode starting April 18th 2022 - GitHub Issues import will be available for review in read-only mode on April 19th 2022 - GitHub Issues will be transferred from “swift-issues-migration” organization to “apple/swift” repository by April 25th 2022 - GitHub Issues will be available for use starting April 28th 2022 ---
**Author:** ![mickeyl](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mickeyl/32/12258_2.png) [@mickeyl](https://forums.swift.org/u/mickeyl)\ **Post date:** [March 22, 2022, 7:16am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/2 "2022-03-22T07:16:06Z")
This is very good news to me. I never got the hang out of Jira and I hope this will increase visibility (and… perhaps reduce the Nirvana-effect that began to spread like a radar) a bit! ---
**Author:** ![YOCKOW](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/yockow/32/20636_2.png) [@YOCKOW](https://forums.swift.org/u/YOCKOW)\ **Post date:** [March 22, 2022, 8:57am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/3 "2022-03-22T08:57:13Z")
Just out of curiosity, I wonder how descriptions in JIRA will be imported to GitHub issues. GitHub adopts markdown, but JIRA doesn't. ---
**Author:** ![stevapple](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/stevapple/32/31979_2.png) [@stevapple](https://forums.swift.org/u/stevapple)\ **Post date:** [March 22, 2022, 4:41pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/4 "2022-03-22T16:41:01Z")
It’s glad to hear that Swift is migrating to GitHub issues! I noticed that you say all the SR bugs will go to `apple/swift`, but we have actually associated bugs with different components on JIRA, and some of them (eg. SwiftPM and SourceKit-LSP) have their own repository. Are we able to migrate these categorized issues into the corresponding repositories? Also would like to know how tags are migrated. Thanks for all your effort to make this happen 🎉🎉🎉 ---
**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:** [March 22, 2022, 5:02pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/5 "2022-03-22T17:02:35Z")
> [@YOCKOW](#): > > Just out of curiosity, I wonder how descriptions in JIRA will be imported to GitHub issues. > GitHub adopts markdown, but JIRA doesn't. The JIRA descriptions and comments will be converted into markdown format. Here is an example: ([SR-15343](https://bugs.swift.org/browse/SR-15343)) ![Screen Shot 2022-03-22 at 9.52.52 AM](https://global.discourse-cdn.com/swift/original/3X/9/2/924af60a3c02249ba7a7dd8cd67b69e0bc31b19a.jpeg) > [@stevapple](#): > > I noticed that you say all the SR bugs will go to `apple/swift` , but we have actually associated bugs with different components on JIRA, and some of them (eg. SwiftPM and SourceKit-LSP) have their own repository. Are we able to migrate these categorized issues into the corresponding repositories? In the second phase we will be moving the issues to the corresponding repositories based on components. > [@stevapple](#): > > Also would like to know how tags are migrated. Yes, we will be migrating components and labels into GitHub Issues label. ---
**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:** [March 22, 2022, 7:56pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/6 "2022-03-22T19:56:10Z")
If you have the same username on GitHub and [bugs.swift.org](http://bugs.swift.org), you should still update the info in [Swift Forums](https://forums.swift.org/my/preferences/profile). ---
**Author:** ![wowbagger](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/wowbagger/32/13847_2.png) [@wowbagger](https://forums.swift.org/u/wowbagger)\ **Post date:** [March 23, 2022, 12:13am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/7 "2022-03-23T00:13:39Z")
How will attachments to bug reports be migrated to GitHub Issues? ---
**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:** [March 23, 2022, 5:11am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/8 "2022-03-23T05:11:33Z")
> [@wowbagger](#): > > How will attachments to bug reports be migrated to GitHub Issues? Attachments will be compressed into one file per issue, and the link will be available in issue description. ---
**Author:** ![masters3d](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@masters3d](https://forums.swift.org/u/masters3d)\ **Post date:** [March 23, 2022, 5:12am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/9 "2022-03-23T05:12:18Z")
What about resolved issues? ---
**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:** [March 23, 2022, 5:13am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/10 "2022-03-23T05:13:12Z")
> [@masters3d](#): > > What about resolved issues? They will show up as closed ---
**Author:** ![michaelhenry](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/michaelhenry/32/21878_2.png) [@michaelhenry](https://forums.swift.org/u/michaelhenry)\ **Post date:** [March 26, 2022, 2:08pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/13 "2022-03-26T14:08:04Z")
Finally!!! It’s way more easy to navigate between codes and issues using github. ---
**Author:** ![xwu](https://avatars.discourse-cdn.com/v4/letter/x/b487fb/32.png) [@xwu](https://forums.swift.org/u/xwu)\ **Post date:** [March 26, 2022, 2:47pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/14 "2022-03-26T14:47:11Z")
There are a number of issues that I’m “watching” on JIRA just to be able to follow any developments. I doubt I’m the only one. Will this be automatically migrated and/or will there be a way export a list from JIRA to continue being subscribed to the same issues on GitHub? ---
**Author:** ![mschinis](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mschinis/32/22318_2.png) [@mschinis](https://forums.swift.org/u/mschinis)\ **Post date:** [March 26, 2022, 6:29pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/15 "2022-03-26T18:29:15Z")
Very exciting news! This should give a lot more visibility to everyone, and reduce duplicate reports! Looking forward to the migration 🙂 ---
**Author:** ![Jumhyn](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jumhyn/32/3891_2.png) [@Jumhyn](https://forums.swift.org/u/Jumhyn)\ **Post date:** [March 26, 2022, 6:59pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/16 "2022-03-26T18:59:33Z")
It appears the "watchers" field on [bugs.swift.org](http://bugs.swift.org) is public, but I'm not sure if there's a way to set those directly via GitHub... perhaps a comment tag would be sufficient? ---
**Author:** ![masters3d](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@masters3d](https://forums.swift.org/u/masters3d)\ **Post date:** [March 27, 2022, 3:02pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/17 "2022-03-27T15:02:32Z")
> [@mishal\_shah](#): > > Update GitHub and [bugs.swift.org](http://bugs.swift.org) username by April 7th 2022 No sure if this is intended but I didn’t not expect this mapping to show in folks public profile. Currently (at least on mobile) if you click on a profile it will shows these fields. Example for me: JIRA Username: masters3d GitHub Username: masters3d ---
**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:** [March 28, 2022, 5:38am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/18 "2022-03-28T05:38:00Z")
> [@xwu](#): > > There are a number of issues that I’m “watching” on JIRA just to be able to follow any developments. I doubt I’m the only one. Will this be automatically migrated and/or will there be a way export a list from JIRA to continue being subscribed to the same issues on GitHub? Going to look into this. Option 1. Add user to `Subscribed` list on GitHub Issues Option 2. `@` all users in comment as watchers ---
**Author:** ![wowbagger](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/wowbagger/32/13847_2.png) [@wowbagger](https://forums.swift.org/u/wowbagger)\ **Post date:** [March 30, 2022, 3:52am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/19 "2022-03-30T03:52:24Z")
A few more questions: JIRA's workflow allows many different statuses and resolutions for each issue instead of just "open" and "closed" for GitHub issues. Will the JIRA workflow be translated to GitHub issues via labels or some other methods? Linked issues on JIRA can be marked as one of "relates to", "duplicates", "blocks", "is blocked by", "cloned from", "cloned to", and "is duplicated by". Upon linking, the linked issue reciprocates. How will this be done with GitHub issues? GitHub can be less accessible for people living in some places. Is it possible to maintain the JIRA site as a mirror of GitHub issues, so _all_ those who currently have access to bug reports will continue to have access to them after migration to GitHub issues? ---
**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:** [March 31, 2022, 10:38pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/20 "2022-03-31T22:38:22Z")
> [@wowbagger](#): > > JIRA's workflow allows many different statuses and resolutions for each issue instead of just "open" and "closed" for GitHub issues. Will the JIRA workflow be translated to GitHub issues via labels or some other methods? The information from JIRA bugs will be included in the description. > [@wowbagger](#): > > Linked issues on JIRA can be marked as one of "relates to", "duplicates", "blocks", "is blocked by", "cloned from", "cloned to", and "is duplicated by". Upon linking, the linked issue reciprocates. How will this be done with GitHub issues? The links will be available in the issue description, and `SR-` link will automatically route to GitHub Issues page. Example: ![Screen Shot 2022-03-31 at 3.35.37 PM](https://global.discourse-cdn.com/swift/original/3X/6/8/68dc7605966fe1796d75f210d4df4ac74cee6dd7.jpeg) > [@wowbagger](#): > > GitHub can be less accessible for people living in some places. Is it possible to maintain the JIRA site as a mirror of GitHub issues, so _all_ those who currently have access to bug reports will continue to have access to them after migration to GitHub issues? Currently we don't have plans to run JIRA mirror for GitHub Issues. ---
**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 7, 2022, 8:22pm UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/21 "2022-04-07T20:22:55Z")
> [@mishal\_shah](#): > > Update Github and JIRA ([bugs.swift.org](http://bugs.swift.org)) username mapping on [forums.swift.org](https://forums.swift.org/my/preferences/profile) by **April 7th 2022** Reminder today is last day to provide mapping. ---
**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 8, 2022, 10:19am UTC](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125/22 "2022-04-08T10:19:07Z")
> [@xwu](#): > > There are a number of issues that I’m “watching” on JIRA just to be able to follow any developments. I doubt I’m the only one. Will this be automatically migrated and/or will there be a way export a list from JIRA to continue being subscribed to the same issues on GitHub? It's possible to export a list of the issues you're watching. 1. Log into Swift JIRA. 2. Click your avatar (top-right) and choose "Profile". 3. Click the "Filters" button (top-right) and choose either "Watched" or "Watched & Open". 4. Click the "Export" button (top-right) and choose from CSV, HTML, etc. [Next page](https://forums.swift.org/t/swift-bugs-are-moving-to-github-issues-and-we-need-your-help/56125.md?page=2)