THIS PAGE IS UNDER TRANSITION...

Overview

JavaFX bug tracking is in the process of moving to the JDK Bug System at https://bugs.openjdk.java.net/. If you have an existing account in the JavaFX JIRA bug tracker, you can file a bug directly as outlined below until the transition is complete.

Most application developers will file a bug at http://bugs.java.com/. After checking that your bug hasn't already been reported, you can click on the “here” link on that page to go to the bug submission form. Choose “JavaFX” as the Product/Category and then select the appropriate Subcategory, Release, and Operating System.

Anchor
FXOverview FXOverview

FX JIRA Overview

JavaFX uses JIRA as its bug tracking database. Our JIRA instance can be found at httphttps://javafx-jira.kenai.com/.

The most important thing you can do when entering a bug report is to ensure that the person who investigates it has enough information to recreate it.  The best way to ensure this is to provide:

...

IMPORTANT:  Bugs that are missing the information needed to recreate them will be closed as 'Incomplete'.  The message that you should take away from this is "there is more work to do before this bug can be processed" and not "we do not care that there is a problem".

Project

Use the Runtime (RT) project for FX bugs.  This is the default.

...

1. Bug - A defect.
2. Feature - New functionality or a significant upgrade to existing functionality.
3. Tweak - A minor enhancement, re-factoring or code cleanup. Tweaks are small in scope. As a rule they should be no more than 2 weeks in duration.
4. Task - A work item that does not change the repository.  Examples: baselining the PRD, open source approvals or architecture reviews.
5. Test - A fix or update to the test suite.
6. Sub-task - A sub item of any of the above.
7. Test - Deprecated - Do not use this issue type.
8. Optimization -  Deprecated - Do not use this issue type.

IMPORTANT: Many processes are different for different issue types.  Unless Unless you are a committer, submit only Bugs or Tweaks.

More Detail About Issue Types

...

OpenFX is divided into components and these are used to assign default ownership of a bug report.  Typically, many bugs are in 'Controls', 'Graphics' or 'Base'.  If you do not know the component, please make your best effort based on the component in Code Ownership.  Unfortunately, the component ownership table does not quite line up with this the choice of components but this will be addressed in future.

Affects Version

//TODO - how is this best chosen, obviously is This should be the version that the person is running but is there more to it?you are running / testing in which you found the Bug.

Fix Version

If this field is present, do not set it or alter it.  This field is for use by committers only.

...

This is the most important part of the bug.  A bug that cannot be recreated reproduced cannot be fixed.  In fact, committers won't make code changes without a test case that shows the problem and then shows the that problem is gone after the fix is applied.

...