Swift bugs are moving to GitHub Issues and we need your help!

Announcements
#1

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 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) username mapping on forums.swift.org by April 7th 2022
    • Go to profile preferences - Swift Forums
    • 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 before creating an account starting today on bugs.swift.org
  • Update GitHub and 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 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
103 Likes
#2

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!

6 Likes
#3

Just out of curiosity, I wonder how descriptions in JIRA will be imported to GitHub issues.
GitHub adopts markdown, but JIRA doesn't.

2 Likes
#4

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 :tada::tada::tada:

1 Like
#5

The JIRA descriptions and comments will be converted into markdown format.

Here is an example: (SR-15343)

Screen Shot 2022-03-22 at 9.52.52 AM
Screen Shot 2022-03-22 at 9.52.52 AM1920Ă—1458 183 KB

In the second phase we will be moving the issues to the corresponding repositories based on components.

Yes, we will be migrating components and labels into GitHub Issues label.

7 Likes
#6

If you have the same username on GitHub and bugs.swift.org, you should still update the info in Swift Forums.

#7

How will attachments to bug reports be migrated to GitHub Issues?

Terms of Service

Privacy Policy

Cookie Policy