JavaFX JIRA issues moving to JBS

Ryan Jaeb ryan at
Fri Apr 17 04:31:54 UTC 2015

I want to highlight something that was clarified for me on the discuss

On the page there's a section entitled "Submit a Code Fix or
Test Case".  I misinterpreted it to be part of the guidelines for
submitting a bug and have been under the impression that I would be
required to follow the linked contributor guidelines, including achieving a
JBS role of author, if I want to submit a bug report that includes a test
case (which is expected as far as I know).

This is not the case.  For anyone landing on, there are
basically no requirements for submitting a bug via the linked form, even if
you're including a test case as part of the bug report.

I'd like to apologize if my misinterpretation inadvertently caused any
misinformation to be spread on this list and I hope the clarification is
useful to anyone that may be making the same erroneous assumption I did.

Ryan Jaeb

On Tue, Apr 14, 2015 at 4:20 PM, Kevin Rushforth <kevin.rushforth at
> 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