Results 1 to 9 of 9

Thread: Oracle Support bug documents

  1. #1
    Senior Member DSauve's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA
    Posts
    1,244

    Oracle Support bug documents

    I was checking on a few of my "favorite" bugs this morning on My Oracle Support, and have noticed that they no longer show the extended details about bugs. Are others seeing this, too? I don't recall hearing anything from Oracle about this information no longer being visible to customers.
    Don Sauve
    Wagstaff, Inc.
    E1 9.2, Win2016, SQL Server 2016, TR 9.2.2.6, WebLogic 12.2.1, BI Publisher

  2. #2
    Senior Member Larry_Jones's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA, USA
    Posts
    3,235
    As a significant part of Oracle's new "Continuous Delivery" Product Roadmap Oracle has decided that "bugs" are a impediment to the new process and therefore are being phased out.
    The truncation of bug details is step 1 in this forward thinking process.
    Larry Jones
    E1 9.2 - TR 9.2.2.6 on Win 2016 R2. SQL Server 2016
    Wintel, BI Publisher

  3. #3
    Member
    Join Date
    Dec 2000
    Location
    Australia
    Posts
    583
    Yep, just checked. I confirm the fargin bastages have removed bug detail. There was some juicy goodness in those full bug feeds. Sometimes even customer names were mentioned which probably wasn't cool. Someone probably decided it was all internal only.

    Live only for today in the Clouds, no past, no future. Flying blind but feelin' fine.

    I take it as a challenge. 20 years in my informal JDE customer support role has been getting boring. Doing it with less information will make more interesting. That and decompiling Java code to figure out what they have stuffed up. But that is just between you and me, mkay?
    Last edited by JEMILLER; 01-29-2019 at 03:45 AM.

  4. #4
    Member
    Join Date
    Dec 2000
    Location
    Australia
    Posts
    583
    Today I have also noticed a large number of search links coming back as:

    ===
    Document cannot be displayed. Possible reasons are:

    The document id was entered incorrectly. Please check and try again.
    The document id does not exist (was referenced incorrectly).
    The document is not classified as publicly accessible ("non-public").
    The content is being updated and it is temporarily unavailable but will be made available again soon.
    ===

    The revisionist historians are busy. Bugs? What Bugs? Oracle has no Bugz!

    The new support portal will end up just being a large animated smiley face. Be happy citizen developers
    Justin Miller

  5. #5
    Member
    Join Date
    Dec 2000
    Location
    Australia
    Posts
    583
    SORTED!

    (At least for now)

    Login to support.oracle.com so that you have your Oracle SSO session established and then plug in the below URL with the bug id set to the one you want detail on.

    https://updatecenter.oracle.com/apps...bugId=16522986

    This is the same JSP that the Change Assistant uses to fetch bug detail. In the case of the Change Assistant search it will only show you bugs for which there are associated ESUs. However, the buginfo.jsp appears to be capable of fetching the bug detail for any bug. So far, every bug I have tried that had no associated ESU, e.g. that was not marked as fixed such as "Rejected", "Returned Reconsider in Future" or "Open" pulled up with detail using this technique.
    Justin Miller

  6. #6
    Senior Member Larry_Jones's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA, USA
    Posts
    3,235
    Thanks Justin!
    Larry Jones
    E1 9.2 - TR 9.2.2.6 on Win 2016 R2. SQL Server 2016
    Wintel, BI Publisher

  7. #7
    Saw this tidbit
    Bug 29297260 : DISABLE FUNCTIONALITY TO VIEW BUG DETAILS IN CHANGE ASSISTANT

    DESCRIPTION OF PROBLEM:
    Viewing of BUG details can display information that raises legality issues.

  8. #8
    Member
    Join Date
    Dec 2000
    Location
    Australia
    Posts
    583
    LOL!

    And strangely that bug is not searchable from the front-end or the JSP link.

    I don't think I have the energy to log a ticket asking for cleansed bug details to be displayed. It won't happen. I get the need to hide customer sensitive data but completely obscuring bug information is just wrong. The bug detail should have comments that are internal only and the rest should be exposed. Perhaps this isn't even about customer data. It is rare that I have seen a customer name mentioned in a bug. I am curious what the legal issues are.
    Justin Miller

  9. #9
    Senior Member DSauve's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA
    Posts
    1,244
    I just checked a few bugs and the bug detail is back!!!
    Maybe Oracle got a bit of feedback :-)
    Don Sauve
    Wagstaff, Inc.
    E1 9.2, Win2016, SQL Server 2016, TR 9.2.2.6, WebLogic 12.2.1, BI Publisher

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.