3

In our game, we have occasional problems w/ IAPs where for whatever reason a purchased IAP doesn't get redeemed, which leads to players requiring aid from the support team.
On our end, a tester reported an issue where he had such problems. 100% reproduction rate, mentioned the affected account to be safe.

Caught the following conversation between two leads regarding that report:

Test Lead 0: Upon rechecking the issue we've discovered that the issue can't be reproduced on our end. We have however confirmed that the one account mentioned in the report is affected.
Test Lead 1: Since we can't reproduce the issue, should we close it?

So, yeah... why bother a poor programmer w/ this issue that is 100% reproducible but w/ one account affected only. Definitely zero chance of fixing at least one instance where this issue might occur.
/s

Comments
  • 2
    Later on it turned out that TL1 misread TL0's comment, thinking there was no reproduction at all, but it wasn't before he was confronted about his idea of dealing w/ the report.
  • 2
    @D-4got10-01 reading is hard hummmmm k ;P
  • 2
    @BordedDev Very. Imagine missing crucial info within the requirements documentation, just because you couldn't have been bothered w/ reading the whole page.

    /* Because the page has a moderate amount of info, that requires scrolling.. but only about 3 pages max. */

    That one happened as well.
  • 2
    @D-4got10-01 Using mouse wheel is hard hummmmm k

    Maybe they need diepsnoek ;P
  • 2
    Why not reopen the ticket, add log data, and let the programmer inspect firsthand?
  • 2
    @rice2 Action has been taken before the report could get closed. But the report mentioned a specific account, which was a dev account, so credentials were there. The programmer had all the info he needed to investigate the issue.
Add Comment