![]() ![]() ![]() Used to approve a backport and to indicate that a porter can begin to work on the bug. This status is reserved for use by Worldwide Support only. Support approved backport - to Development. Used when an operating system problem is the cause of the bug, to indicate that, following verification, the bug filer should update to Status 95. (Use only when the product or platform is near the end of its lifecycle or when the fix would require a major re-write). Used to indicate that the bug will not be fixed and that filer should approve by updating the bug to Status 84: Closed, Not Feasible to Fix. Used to indicate that the bug will not be fixed and that filer should approve by updating the bug to Status 83: Closed, Product/Platform. Used to show that bug is waiting for another bug to be fixed. When the codeline is opened, status will be changed to 40. Used to indicate that a backport has been approved and is waiting for codeline to open. Used to request verification of the bug fix from bug filer and to request that integration merge the fix into the base code. Used to notify filer that the bug is a duplicate. Used to request verification of the bug fix from bug filer. Used to notify filer that the work has been suspended until information is received. Suspended, Required information not available. Used to notify filer that bug was not valid. Used to notify filer that bug cannot be reproduced. Used to request more information from the bug filer. Used to notify filer that bug is waiting for a development resource to become available to work on it. Used to send an enhancement to Development to be included in a release. Used to send an enhancement to product managers for scheduling. Used to request a product enhancement cost estimate from product managers. Used to request more information from the filer. Used to include the enhancement in the report for the User Group. Used by the Oracle Support engineer to pre-sort well-formed bugs before development start fixing. Used to send an enhancement to Oracle's product managers. Used to keep track of bugs which are fixed by third party companies. Used to request documentation enhancement. ![]() Used to send an enhancement to Oracle User Group review. Used to indicate that the bug is ready for Development, or to indicate that additional required information has been provided for a Status 30 bug. Used to file a bug without all the needed information (for instance, trace files from the customer), to inform Development that a bug will soon become Status 11. If the bug is associated to an SR, click a related SR link to view the details. To view the details of a bug, click a bug number link. To add bugs from favorite SRs to the Bug Tracker region, click Add Bugs, select the box next to Bugs Associated with x Favorite SRs, then click Add as Favorites.Ĭlick the View menu in the upper left of the Bug Tracker region to add or adjust the data columns, change the order of the columns, or export your bug list. Click the x on the left side of the Bug Tracker region to clear the advanced filter. For example, you can filter by SR, SI, status, update dates or SR severity. Click Advanced to filter the bugs displayed. To search for bugs within the Bug Tracker region, enter search criteria in the Search box, then click the magnifying glass. It is displayed whether it is open or closed and remains in the Bug Tracker region until you unmark it as a favorite. If you mark a bug as a favorite, either on the SR Details page or while searching, the bug automatically appears in the Bug Tracker region. Click Advanced to use the advanced search filter.īugs that are associated to SRs that you mark as a favorite. To search for bugs with the Oracle Bug Database, select Bug Database in the global search box, enter search criteria, then click the magnifying glass. Only published bugs and enhancements are displayed.īugs that you marked as favorites within the SR Details page.īugs that you mark as favorites while searching. Bugs are created by Oracle Support engineers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |