Unanswered Question
Apr 10th, 2010
User Badges:

I'm not sure if the "documentation" in BugToolKit comes under the purview of this group but if it does, please look into the declining standard of published bug information. For example, see CSCtd00411. Other than that I can infer from it that others are also seeing this same problem (which exactly describes what I'm facing), it tells me nothing.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Rob Huffman Mon, 04/12/2010 - 06:50
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Benjamin,

There is a whole new Community dedicated to these exact type

of questions

Online Technical Support Tools Community - NEW - Bug Toolkit Community

Our new Bug Toolkit Support Community allows you to provide your input on this tool!  We're hoping you'll visit the subcommunity and participate and provide us with feedback on bug toolkit and ways you'd like to see the tool enhanced/improved!

The Bug Toolkit Business Team




Please support CSC Helps Haiti



Phillip Remaker Tue, 05/04/2010 - 13:30
User Badges:
  • Cisco Employee,

The Release Note in Bug Toolkit exists to describe the problem and workaround.

In some cases, you have to wait until the bug is fixed before you get any relief.

What is your question about the bug?  From my read of the release notes, it seems like the error is generated incorrectly.

Release notes are generally written directly by engineers; no professional documentation editors intervene.  In the current edition of the bug, it seems that they are referring to an internal tracking tool, and that should be edited out.

The bugs is assigned to be repaired, but it seems that the error is spurious and can be ignored. 

How would you edit the bug?


This Discussion