Now, after my first blog post on reporting bugs, you're in the right mood to start selling your issues. But you might be in the mist on what I mean with to-the-point repro scenario. If so read on; if not ... also read on, don't be afraid to learn.
To-the-point means to me that the repro scenario will lead the engineer straight forward to the bug you are reporting. No need for her to spend too much time to get it reproduced. Just remember: the faster reproduced, the faster - and often better - it get fixed!
So how to lead the engineer in a straight forward manner to the result? By describing:
But … it’s not only the wording that does the trick. It’s also how you present them. The better the layout the easier to read and execute upon.
So how would that look like in a real world case? I'll show you one example based on an incident reported to MS (incident 9594805).
In NAV 2009 SP1 report Sales Quote (REP204) fails when I execute it from the sales quote window (FOR41) with "Sell-to Customer No." = '' AND "Sell-to Contact No." <> ''[so "Sell-to Customer No." is empty while "Sell-to Contact No." is populated]The thing is that when I create a new contact (of type Company) I can create a sales quote for that new contact, but I cannot print it.
The error does not exist on NAV50SP1.
NAV2009 SP1 RTC (w1, but also on other country versions like NL and DE)
Using CRONUS demo database no preparatory actions needed.
No. = TESTType = CompanyName = Luc van VugtAddress = My Street 41Post Code = 1234 MSCity = MyCity
Click 'ENTER' to let system insert a number ('No.') for the quote
Following fields will be populated by the system:
Sell-to Contact No. = TESTSell-to Customer Name = Luc van VugtSell-to Address = MyStreet 41Sell-to Post Code = 1234 MSSell-to City = MyCityOrder Date = 27-1-2011Document Date = 27-1-2011
Type = ItemNo. = 1000Quantity = 2
Error message: Customer No. '' does not exist.
Report will run and show preview of sales quote for contact TEST with right details (as entered on quote as above).