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