Page History

...

 What if the change you want to downport is not public?

Sometimes a change you want to downport is not public in JBS. This means you can see the change and its JBS ID in the Git repository, but you will not find the corresponding issue in JBS.

In such a case, you have to create the corresponding backport issue manually, according to the following recipe:

1. Create a new issue in JBS with type "Bug" (you can't directly create an issue of type "Backport")
2. The new issue should have exactly the same summary like the original change. You can take this from the Git "summary" line by stripping the prefixed Bug ID.
3. It's helpful if the bug description contains a link to the original commit.
4. Affected version should be one of "8", "11", ...
5. Under "Linked issues" choose "backport of" and enter the bug id of the change you want to downport into the "Issue" filed (in the format "JDK-XXXXXXX"). After adding this link, it will be not visible. You can only verify that you added it by looking at the histrory. 
6. Once you've filled out all the other fields, press "Create" and once the issue has been created, edit the issue "Type" and change it from "Bug" to "Backport".
7. Continue as usual at step 2.

What if the JBS issue is visible, but the commit went to an internal repo of Oracle?

1. Obviously, you You can not see the implementation of the fix. You need to craft the change by your own. 
2. For the PR, use title "backport JDK-<jbs bugid>" and handle it as any other backport.  Example

...