...
Creating Jira issues from GitHub issues
Commenting on a GitHub issue can make Labelling a pull request will create a Jira issue.
Q: How do we find the Jira project to use?
An explicit mention in the comment. No: too labor intensive, error-prone, and repetitive.
The issue’s repo has an associated Jira project (somehow).
The issue is on a project board, and the project has an associated Jira project (somehow)
The label is
jira:2u. Other organizations will be able to participate with their own labels.A configuration file will have a mapping from repo to Jira project. Ned Batchelder will update the configuration as teams need.
The GitHub issue will then get another a comment with a link to the Jira issue.
Q: is there a better way? GitHub issues don’t have arbitrary links out.
The Jira issue will have a link to the GitHub issue.
I think we already have a field for this? “customfield_10904” (known as URL, but there are multiple fields called URL)pull request.
It will be in the body of the Jira issue.
We aren’t using any custom fields: their availability isn’t uniform across projects.
Creating GitHub issues from Jira issues
Q: Will it be enough for phase 1 to not do this?We are not doing this now.
Syncing information between Jira and GitHub
...
There is no synchronization between Jira and GitHub: changes on either side are not transmitted across.
...
Below here is the content of the page from November 2022:
...