The bugzilla app is continuing to evolve; I've been speaking with some individuals at BMC, and in order for the site to help BMC help us, I would like to post a set of expectations, via scenario, for using the app. The defect id is the key for BMC to correlate their internal efforts to the defects and rfe's in the bugzilla app; these guidelines are to help ensure that information is available.
For Defects: 1. Customer 'A' encounters a potential defect within AR System. 2. Customer 'A' checks ARSWiki to see if a defect already exists for the symptoms seen 3. If the defect already exists, Customer 'B' adds his name and/or vote to the defect in ARSWiki if they want. 4. If no defect already exists, Customer 'A' posts his findings as a "potential" bug in AR System to ARSWiki 5. Simultaneously, Customer 'A' contacts BMC to confirm that the issue is a defect. 6. If the issue turns out not to be a defect (either through interaction with ARSList or with BMC Support), the outcome is posted by Customer 'A' to ARSWiki and the issue is marked as "not a defect". 7. If the issue is a defect and duplicated by BMC, Customer 'A' updates the ARSWiki page to include the SW defect ID for the defect. 8. Now other customers can see that BMC has logged the defect and Customer 'A' can keep the ARSWiki page up to date with the current status ** I have to say, the search capabilities of the bugzill app are pretty good. It should be rather easy to find things using a search. For RFE's 1. Customer 'B' comes up with a potential RFE for AR System. 2. Customer 'B' checks ARSWiki to see if an RFE already exists for the idea 3. If the idea already exists, Customer 'B' adds his vote to the RFE if they want. 4. If no rfe already exists, Customer 'B' posts his idea as a "potential" RFE in AR System to ARSWiki 5. Simultaneously, Customer 'B' contacts BMC to log the RFE officially with BMC and obtain the RFE #. 6. Customer 'B' updates the ARSWiki page to include the RFE ID. 7. Now other customers can see that BMC has logged the RFE and Customer 'B' can keep the ARSWiki page up to date with the current status I know it may be tough to find the defect id's for some of the bugs people have submitted, but I want to encourage people to hunt them down and update the defects. For those entries on the Bugzilla site that do not have a defect registered with BMC, I want to encourage you to register them with BMC (yes, I am guilty of this). The long term goal of the bugzill app is that BMC can redo the defect and rfe portions of the supportweb site and incorporate many of the good ideas present in the bugzilla app at some point in the future. The short term goals are (1) to provide visibility to people as to the defects and rfe's against the products and (2) provide the priority of each. based on votes, to BMC. As a short, unrelated topic, I want to outline one of the capabilities of Bugzilla: - when a user performs a search, they can customize which columns are shown in the search results by clicking the 'Change Columns' link at the bottom of the search results. Useful columns may include 'Vendor Bug ID' or 'Votes', depending on which side of the table you are on. Thanks, Axton Grams _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
