Results 1 to 19 of 19
  1. #1
    Brand / Commerce Manager Tolero's Avatar
    Join Date
    Sep 2007
    Posts
    6,517

    Arrow New Bug Reporting Tool Now Available!

    We've updated our bug reporting tool for DDO! This new tool will allow us to receive and review many more bugs than our previous system, and is accessible both in and out of the game.

    Important Notes:
    • You do not need a forum account in order to access the new bug reporting tool.
    • The new system provides more guidance during the bug submission process, asking for more details regarding certain types of bug reports.
    • The old bug reporting system link may appear in some areas of the website. Please disregard these links, as they will be overwritten during the DDO website updates this month.
    • If you have previously had difficulty with the bug reporting tool (e.g. you aren't sure that your bug actually went through in the old system), you are welcome to resubmit a bug in the new tool.
    • The new bug reporting tool is most compatible with Firefox and IE browsers, though it will also work in Chrome and Safari browsers.

  2. #2
    Community Member gphysalis's Avatar
    Join Date
    Jun 2010
    Posts
    893

    Default

    You should add a check all box for unlocked epic destinies
    Quote Originally Posted by Eladrin View Post
    Grease is the only party buff
    Quote Originally Posted by MajMalphunktion View Post
    talk about your exploits
    Quote Originally Posted by Memnir View Post
    DDO is not PnP. This is by design

  3. #3

    Default

    \o/
    Brenna / Tzanna, The Dancing Rogues of Argonnessen
    Ascent on Argo
    "As the party's resident trap expert ..." <dies with smug yet surprised expression on face>

  4. #4
    Community Member dopey69's Avatar
    Join Date
    Nov 2007
    Posts
    1,161

    Default

    Quote Originally Posted by tolero View Post
    we've updated our bug reporting tool for ddo! This new tool will allow us to receive and review many more bugs than our previous system, and is accessible both in and out of the game.

    Important notes:
    • you do not need a forum account in order to access the new bug reporting tool.
    • the new system provides more guidance during the bug submission process, asking for more details regarding certain types of bug reports.
    • the old bug reporting system link may appear in some areas of the website. Please disregard these links, as they will be overwritten during the ddo website updates this month.
    • if you have previously had difficulty with the bug reporting tool (e.g. You aren't sure that your bug actually went through in the old system), you are welcome to resubmit a bug in the new tool.
    • the new bug reporting tool is most compatible with firefox and ie browsers, though it will also work in chrome and safari browsers.



    lol

  5. #5

    Default

    Quote Originally Posted by Tolero View Post
    We've updated our bug reporting tool for DDO! This new tool will allow us to receive and review many more bugs than our previous system, and is accessible both in and out of the game.

    Important Notes:
    • You do not need a forum account in order to access the new bug reporting tool.
    • The new system provides more guidance during the bug submission process, asking for more details regarding certain types of bug reports.
    • The old bug reporting system link may appear in some areas of the website. Please disregard these links, as they will be overwritten during the DDO website updates this month.
    • If you have previously had difficulty with the bug reporting tool (e.g. you aren't sure that your bug actually went through in the old system), you are welcome to resubmit a bug in the new tool.
    • The new bug reporting tool is most compatible with Firefox and IE browsers, though it will also work in Chrome and Safari browsers.
    I want to believe...I do.

    No really.

  6. #6
    Community Member
    Join Date
    May 2009
    Posts
    26

    Question report follow up?

    Any chance that players will be able to refer back to bug reports filed, and see a simple status follow up?

    Something short and simple, such as:

    - WAI
    - More info required
    - known issue
    - Under investigation
    - fix in development

    While a new bug reporting interface that is more user friendly and stable is great, my issues with the old system were bug reporting seemed a useless endeavour. The reports seemed to go straight to the great unknown.

    Personally, I need to feel like spending my time bug reporting has an effect.

    Getting some kind of feedback on my report would go a long way!

  7. #7
    Hero
    and Mo Bro H'ro
    ComicRelief's Avatar
    Join Date
    Aug 2010
    Posts
    486

    Default Finally - A Decent Attachment Size Limit

    Good to see that the file attachment limit has been raised to 10 files and 25MB. That 1-file, 1 MB limit was insanely low...even 7 years ago.
    "...At least it tells us they understand our language; they're just not willing to speak to us in it. -Who knew they were French?"

  8. #8
    Community Member
    Join Date
    Aug 2010
    Posts
    334

    Default

    Is there a reason this new bug reporting tool requires a full name?
    Quote Originally Posted by submit a bug
    Contact Info
    * Full Name:

    * - required field(s)

  9. #9
    Community Member Shade's Avatar
    Join Date
    Feb 2006
    Posts
    14,425

    Default

    Another "We won't respond to your bugs, or even really read them tool"

    Zero transparency, zero use.

    Guys please use the proper, ACTUAL, (relatively) new and actually functional bug reporting tool - The bug report forum.

    They read every bug on there, and respond to the all the major ones. Most of the top discussed ones even got fixed.

  10. #10
    Brand / Commerce Manager Tolero's Avatar
    Join Date
    Sep 2007
    Posts
    6,517

    Default

    Quote Originally Posted by peng
    Is there a reason this new bug reporting tool requires a full name?
    First name or play name is fine, will make sure they change that. Just gives us something we can call you other than "dear @gmail...."

    Quote Originally Posted by Shade
    Another "We won't respond to your bugs, or even really read them tool"

    Zero transparency, zero use.

    Guys please use the proper, ACTUAL, (relatively) new and actually functional bug reporting tool - The bug report forum.

    They read every bug on there, and respond to the all the major ones. Most of the top discussed ones even got fixed.
    So let's talk a little bit about the differences in the tool from the old one to the new one. The new tool allows us to aggregate and sort large volumes of bug reports quickly. Previously we received them as one-by-one items that we had to then click-open one-by-one, and any responses were also one-by-one. The form itself was one-size-fits-all bug reports. Additionally because the system was tied to forum, forum log out timer issues impacted the tool (manifesting as "I was writing my bug, I hit submit, but then it took me to the home page instead of giving me the confirmation screen"). Obviously this left a LOT of room for improvement. Thus the new tool.

    We're now able to gather up the submitted bugs in great quantity and organize them into patterns. This allows us to more quickly quantify what bugs people are reporting most often, rule out false positives, get more accurate known issues based on volume, reach out for more details where needed, etc. The form itself provides more guidance/field options per issue to allow us to drill down into deeper information that can be important for particular types of bugs. We can sort and categorize the reports in ways that expose patterns much better (and more efficiently) than we could previously. "That's odd, we had a spike in reports from Monks about X after we turned on Y" "Ok, what are those reports saying... oh hey look, they're all mentioning Z in their reports". This is a level of detail that was very manual under the old system, and the time spent gathering/organizing it into something useful and actionable for a dev was molasses slow.

    The "is this a bug" forum is very useful for collaboration, but it's highly manual to review on our end. We have to open each thread one at a time to see what tasty info is inside.

    Now that the new system is in place, we'll see where the data takes us!

  11. #11
    Community Member Mindos's Avatar
    Join Date
    Jan 2010
    Location
    flying underneath
    Posts
    631

    Default

    can I report that the trackers are not listing dev names, and only a chevron, or gitgo or something or other///...

  12. #12
    Community Member eterna1_drag0n's Avatar
    Join Date
    Sep 2009
    Location
    Pennsylvania, USA
    Posts
    77

    Default

    The old bug reporting tool has jaded me beyond comprehension, combined that with the known bug list which gets longer with every update; i am not going to use the new one, until there is a drastic increase in the output of bug fixes.

    Oh btw;

    Hirelings won't attack a dryad's tree. Found out in a solo elite Overgrowth last night.
    Khyber: mislabeled, thekeymaster, nondevout, five

  13. #13
    The Hatchery Nibor's Avatar
    Join Date
    Jul 2010
    Posts
    703

    Default

    Quote Originally Posted by eterna1_drag0n View Post
    Hirelings won't attack a dryad's tree. Found out in a solo elite Overgrowth last night.
    This is an example of a bug that needs more details - I have been running king's forest with hirelings over the last couple of days and they attack the dryad trees just fine. This may be specific to the hireling, the tree, or even a combination of hireling/tree; what hireling, which tree (/loc data)?

  14. #14
    The Hatchery Nibor's Avatar
    Join Date
    Jul 2010
    Posts
    703

    Default

    So, I see that when I open the bug report form in-game the location field is autofilled - that's wonderful! Will make reporting bugged ladders quick and painless, for example.

    Why isn't other data able to be auto-filled? At least the server field? Hopefully the character details as well.
    *nudge*nudge* this would be an excellent reason to have character export APIs still in place....

  15. #15
    The Hatchery
    Join Date
    Jun 2010
    Posts
    2,649

    Default

    What category would "stealth/sound detection/invisibility is broken" go under? There's no "game mechanics" category. I just put it under "other".

    Quote Originally Posted by eterna1_drag0n View Post
    i am not going to use the new one, until there is a drastic increase in the output of bug fixes.
    "I'm not going to help you fix more bugs until you're already able to fix more bugs."

  16. #16
    Community Member Systern's Avatar
    Join Date
    Sep 2011
    Posts
    913

    Default

    Time to Tar and Feather Gazebo!

    Tried to submit a bug, with an attached screenshot.

    "could not connect to Upload Server".

    Bug submission is hanging there now, "Finish..." is greyed out.

    I'm using Chrome, if that matters.



    FYI, The bug... After Relogging, this happens:


  17. #17
    Community Member
    Join Date
    Sep 2009
    Posts
    603

    Thumbs up Seems to be a very important step forward

    Quote Originally Posted by Tolero View Post
    We're now able to gather up the submitted bugs in great quantity and organize them into patterns. This allows us to more quickly quantify what bugs people are reporting most often, rule out false positives, get more accurate known issues based on volume, reach out for more details where needed, etc. The form itself provides more guidance/field options per issue to allow us to drill down into deeper information that can be important for particular types of bugs. We can sort and categorize the reports in ways that expose patterns much better (and more efficiently) than we could previously. "That's odd, we had a spike in reports from Monks about X after we turned on Y" "Ok, what are those reports saying... oh hey look, they're all mentioning Z in their reports". This is a level of detail that was very manual under the old system, and the time spent gathering/organizing it into something useful and actionable for a dev was molasses slow.

    The "is this a bug" forum is very useful for collaboration, but it's highly manual to review on our end. We have to open each thread one at a time to see what tasty info is inside.

    Now that the new system is in place, we'll see where the data takes us!
    I do feel a bit amazed you guys managed without all that sorting so far, no wonder people were often getting frustrated with a lack of reaction to them! Makes me curious to see the next update/patch.

    One thing I would embrace, is if you could give some rough information on what issues are on, how much it is after what patches/updateds for example in the weekly news round.

    Thanks for the work guys

  18. #18
    The Hatchery
    2014 DDO Players Council
    Backley's Avatar
    Join Date
    Sep 2009
    Posts
    1,543

    Default Not usable

    The new bug reporting tool is not usable: if I try to enter a new bug, I have to re-enter all of my info all over again, even though 95% of the info will always be the same. On the old bug reporting tool I could at least get around this by entering a bug, getting the confirmation screen, then using Back to get back to the completed form which I could update for the next bug.

    Attempting to do this on the new bug report tool just gives an "Invalid Token/Session" error when you try to submit the 2nd bug.

    Using this new tool is too onerous and I won't bother entering any more bugs unless I can use Back to enter the next one and/or the form remembers my entries from last time. I'll see if I can find a Chrome plugin that remembers this all for me or something.

    Also: the confirmation email after a bug is submitted doesn't tell me anything about the bug I submitted, so I can't tell what issues have successfully been submitted. The old system would tell you the subject you put on the bug at least. The confirmation email should list everything that I submitted, in case I need to refer to it later.

    Edit: Also put a link on the confirmation page to "Report another bug."
    Last edited by Backley; 04-13-2013 at 09:58 PM.
    Author of Info Blue UI Skin (Really wish Turbine would update the skinning interface and enable all the new UI parts.)
    If you don't have an SSD, you should be using DDOPreload (fixes the slow first login issue)

  19. #19
    Founder Hambo's Avatar
    Join Date
    Feb 2006
    Location
    Sacramento, Ca.
    Posts
    3,784

    Default

    Quote Originally Posted by Qezuzu View Post
    What category would "stealth/sound detection/invisibility is broken" go under? There's no "game mechanics" category. I just put it under "other".



    "I'm not going to help you fix more bugs until you're already able to fix more bugs."
    I would say that "Other" is the perfect place for these type of reports. If the reports are easier to review and classify, it won't be long until we see new categories to use as the "Other" group becomes a larger percentage of reported problems.
    Carpe D.M.! (Sieze the Dungeon Master!)
    Founder #2003 - Interocitor Repair - Call for discount prices

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload