JavaFX JIRA issues moving to JBS

Stefan Fuchs snfuchs at
Wed Apr 15 02:58:49 UTC 2015

Hi Kevin,

while I appreciate the consolidation of the bug tracking systems, I have 
some questions about the JBS.

Having filed some jdk-bugs via in the past, I never got 
any feedback, if the bug has been accepted and if an JDK bug has been 

For example three weeks ago, I filed a bug about a regression in the 
ssl-engine in the Java 8u60-ea release.
I got an email that the report is evaluated containing a Review ID: 
The next day someone from oracle requested unspecified files as 
attachment under the Incident Report 9055609.
I replied that I think, I provided all information needed to reproduce 
the problem and asked about, what specific files he meant.
Since then I never heard anything back.

So my question is, how does the web frontend process work at oracle?
Is there any documentation about it?
Can I somewhere look up the status of an review or incident report?
How I'm supposed to know, that the Review ID and the Incident Report ID 
are related?
(I filed only one bug, so this time it was easy for me)
Will I get information with bug id, if a bug has been created in the JBS?
Will I get an email, if the request has been rejected?
How long does the review process normally take?
Is there an escalation level?

It would be nice, if the initial mail would contain the data from the 
web form, so I could keep it for reference and to verify that all 
information, has been successfully transmitted.

One last question about the migration. I have several bugs on my 
watchlist. Will I continue to receive update notifications for this bugs 
after the migration?

-- Stefan

Kevin Rushforth wrote:
> As most of you are aware, JavaFX uses its own JIRA bug tracker [1]. 
> The JDK Bug System [2] (JBS) is the JIRA bug tracker used by the 
> OpenJDK Community. With the OpenJFX Project being a part of this 
> Community, it is time for us to move away from our separate bug 
> tracker and make use of JBS. This will allow us to leverage the 
> greater infrastructure investments being made and lessen the burden of 
> having to maintain our own infrastructure, and consolidates all JDK 
> bugs in one place. The target date for this transition is the second 
> half of May.
> The issues currently in the RT project in JavaFX JIRA will be folded 
> into the JDK project in JBS. Details will follow on the mapping, but 
> here are the highlights:
> - A new "javafx" component will be created in the JDK project
> - Most existing JavaFX JIRA components will be sub-components of the 
> "javafx" component
> - The mapping from existing "RT-nnnnn" bug ID to new "JDK-mmmmmmm" bug 
> ID will be maintained by JBS such that searching for RT-nnnnn will 
> take you to the right JDK-mmmmmmm bug.
> A JBS account will be needed to directly report new bugs or comment on 
> existing bugs. Most application developers will file new JavaFX bugs 
> at [3] just like other JDK bugs. The requirement to get 
> a JBS account [4] is to have a role of Author or higher in an OpenJDK 
> Project (e.g., jdk9 or openjfx).
> Our advice to those of you actively involved and participating in the 
> OpenJFX Project is to consider joining the OpenJDK as a Contributor 
> [5] by signing the Oracle Contributor Agreement (OCA) [6]. This is a 
> necessary first step in contributing to any OpenJDK Project, including 
> OpenJFX. It allows you to provide patches that we might accept for 
> OpenJFX, and is also a step along the path to becoming an Author. The 
> general guideline [7] is that the Author role may be requested by a 
> Project Contributor who has contributed two non-trivial patches that 
> have been accepted and pushed.
> As part of this transition, we will enable anonymous viewing of bugs 
> (no need to login just to look at a bug) and they will be easily 
> searchable online.
> We apologize for the inconvenience caused to OpenJFX Participants by 
> this upcoming change to the bug database write access policy. We 
> really appreciate your commitment to improving and growing the JavaFX 
> technology.
> -- Kevin
> [1]
> [2]
> [4]
> [3]
> [5]
> [6]
> [7]

More information about the openjfx-dev mailing list