Thursday Mar 13, 2014

How-To: Searching for list of bug fixes in a given AutoVue version

I wanted to add to the couple different posts I submitted in the past on how to track and understand Bug reports in the My Oracle Support (MOS) portal. I've received the occasional question from customers and partners regarding where to find a list of bug fixes for a given version of AutoVue (e.g. in order to evaluate the potential advantages of upgrading, beyond the product enhancements outlined in the Release Notes hosted on the documentation website).

The easiest way to view the bug fixes for a given version of AutoVue is through the Advanced Search feature in the MOS portal, which allows you to search the Oracle BugDB based on the specific products and version number you're interested in. For example to search for the list of bugs fixed in AutoVue 20.2.2:

  1. Log into the MOS portal
  2. Click on 'Advanced Search' in the upper-right corner
  3. In the Advanced Search dialog, specify the following:
    • Source: Bug Database
    • Related to the Product: Add all 5 flavors of AutoVue (Oracle AutoVue Office, Oracle AutoVue 2D Professional, Oracle AutoVue 3D Professional Advanced, Oracle AutoVue EDA Professional, Oracle AutoVue Electro-Mechanical Professional)
    • Fixed in Version: 20.2.2
  4. Click on 'Search'

If needed you can further refine the search by keywords - e.g. if interested in fixes related to specific file formats, platforms, features, etc.

Also if you have questions regarding any of the bugs or enhancements listed as fixed/implemented in a given AutoVue version, feel free to post into the AutoVue Community and our team will be happy to follow up.

Friday Jan 06, 2012

Understanding Oracle’s Bug Status Codes for AutoVue

I’ve seen a few questions in recent months regarding the various status codes that Oracle uses to indicate the current status of bugs logged in the My Oracle Support (MOS) system. The status code of a given bug can be seen by opening the bug report in MOS and looking for the ‘Status’ field (which is at the top-left of the report):



Yes, there are a LOT of bug status codes used at Oracle (more than 50 of them), and different product groups at Oracle may use the codes in slightly different ways.

The good news is that the AutoVue group uses a relatively small subset of these status codes, and for the most part uses them in the same way as other Oracle groups. Our Support team outlines this – including details of our one “special-use” status code (status 16) – in the following KM Note:

Note 790873.1 - Oracle Bug Status Codes for AutoVue Product Family

For those of you tracking the status of any bugs for your AutoVue/VueLink/DPS products, make sure to read through the KM Note so that you’re familiar with the status code flow and can easily tell where a particular bug is in its fix lifecycle.

About

The authors of this blog are members of the AutoVue Enterprise Visualization team at Oracle. The views expressed on this blog reflect those of the members and do not necessarily reflect the views of Oracle.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
24
25
26
27
28
29
30
   
       
Today