Advertisement
Guest User

Untitled

a guest
Jul 22nd, 2017
64
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.12 KB | None | 0 0
  1. The Issue Tracker Full Guide V1
  2. Welcome to the full guide on how to work with and use the issue tracker on the eternal-wow forums. Before we begin, let’s explain what the issue tracker is. The issue tracker, a tracker of issues, is an electronic based issue report section and virtual tracking device for the Eternal-Wow server. This allows the developers and staff to track and fix issues players have reported from any of the realms. The tracker contains different sections, which are broken down in this guide; this guide also has examples of posts and what to do in different situations.
  3. The Issue Tracker Layout.
  4. Change Log >
  5. The change log is the place of places, the home town of the fix records. This is a place where senior developers will post fixes / change logs. This is a great place to find out if the issues that you are looking at have been looked at and or fixed. Please take into account, some issues that have been reported as fixed, can pop up time and time again, as some fixes are only temporary and or will need to be re-run after updates, developers will do their best to keep up with the re-running of these fixes.
  6. Known Issues >
  7. As we see a lot of the time we get a lot of double or triple posted issues regarding the same topic.
  8.  
  9. The main reason being is that people post an issue on the issue tracker so that us the staff are aware of the issues and so that we can attend to them being fixed. Now a lot of the double and triple posted issues can be either hard to fix issues or issues that the emu provided will have to fix. That means some issues could he posted about various amounts of times which when we only need 1 report to make us aware of the problem.
  10.  
  11. The new Known Issues Forum is that which is now hoping to stop the intended and helpful issues being reported over and over again and it works like this. A staff member either a helper or a dev will see that an issue has been reported many times and they know this is one of which that does or may cause upset between players and game play on the realms. This issue will then be looked at, reviewed and posted about on here. They will include related issues, eta on fix dates I'd possible and a run down on the issue. The topic will be locked so that you can't post on the thread since we know the information needed to be posted on here but you may contact the staff member reporting the issue via pm on the forums.
  12.  
  13. What is this for? The main reason this has been introduced is to cut down and or stop multi threads on the same topic raised on the tracker and to save time making both our lives easier since you will not need to post about the issue and can continue playing on the realms.
  14.  
  15. But what if the issue has not been reported on here? You can expect any off the following 3 out comes to be correct.
  16.  
  17. 1 - A staff member is in the process of looking into the issue and is gathering information needed to be posted on the Known Issues Section.
  18.  
  19. 2 - A staff member is aware of the problem and thinks that the resolve time off the issue will be sort and does not see the need to report it in here, if so you will be able to find the current issue on the issue tracker with a staff reply, with all the relevant information needed thus not needed a second report to be made.
  20.  
  21. 3 - The issue has not been reported and will require you to search in the report an issue for the issue or make a thread about the topic.
  22.  
  23. So if you see your problem in here that means you do not need to make a topic on the issue just wait until further updates and information is released
  24. Report a Player >
  25. This is an external link; you don’t need to worry about this.
  26. Report an Issue >
  27. General Issues >
  28. General issues. So what is a general issue? This can be any type of issue that doesn’t relate to any of the other subjects players can report, this can be from login issue, player reports which seem to end up there anyway, or random issues that people can be bothered to place in the correct place anyway.
  29. Player vs. Player Issues >
  30. Player vs. Player issues is also known as PVP issues. This can be anything do to with killing another player in any way shape or form, from arena, battlegrounds, world PVP or PVP issues in general.
  31. Player vs. Environment >
  32. The player vs. Environment sections is all about PVE or instance issues. This can also range to general dungeons, raids or world boss mobs.
  33. Quest and Levelling Issues >
  34. This can be anything do to with general levelling issues, from quests, bugged npcs, chain lines alike. This could include quests from instances, levelling roads from remorse e.c.t e.c.t.
  35. Class Issues >
  36. Class issues, this can include any type of class issue, from spells to talents, quests (class specific) or any other class related bugs.
  37. Trash reports >
  38. This is where you place any trash reports you find.
  39.  
  40. So how does this “Report an Issue” work? Players will report there issue into the certain sections. It is your job to search each of the above sections for issues that have been reported. It is your main role to test these issues and move them to the confirmed section so our developers can look at the issue and fix it. You will need to make common sense decisions and make choices based on your research. I can’t stress that good English and common sense is vital on replies, as all of the posts must have a reply.
  41. So when you see an issue you must do one of two things. If the issue has enough information and isn’t what we want to call a bad report then you must move it to pending, this means that it has enough information to be looked at, this helps you to power through and sort out completely useful reports into a pile, which then can be sorted through at a later date, even though a lot of people address the issue straight from the tracker. If the issue is completely crap, then move it to the trash reports, you don’t have to leave a response for these.
  42. Once you have moved an issue to the pending section you will then need to address the issue, which means to check it out and to make sure that it is actually a issue on our servers. If it is website related, reply and tell them this is in the wrong section, all VIP and Vote problems should be moved to pending where a higher member of staff will take a look at the reports.
  43. When checking out an issue, make sure to be a quiet and discrete as possible, if a problem requires you to join and run an instance, then do so, but make sure to act professional at all times. GM’s will not be able to help you with in-game testing, but you can contact a developer if you are unsure with something’s, for example, creature spawns or tables that might be wrong.
  44. If the report comes up and it’s not an issue, and you are 100% that it’s not an issue, then move it to the declined issue reports. If it is an issue, move it to the confirmed issue section, and make a reply on the post, saying thank you to the user, and make your own little report on it, include any extra links e.c.t that developers may need.
  45. So let’s get down to some examples.
  46. It seems that there is the alchemy trainer in shattrath but when you train alchemy, it seems that you cant even make anything since when you click the alchemy skill the pop up for profession does not come out. Is it bugged or can you really not get alchemy?
  47.  
  48. Ok so for this report, we can see clearly that there is a supposed bug with alchemy trainers in shattrath. So for this, you would firstly need to make a reply saying, we will test this out. Thanks for the report and move it to the pending section. Then you would need to head over to Shattrath and test out the Alchemy trainers for both horde an alliance to make sure that this bug is correct. If it is then you need to move it. You would also need to include a link to the npcs you have confirmed bugged, so the developer doesn’t need to run around trying to find it.
  49. While me and pals were able to down Putricide in ICC10 - since the fight worked properly for the most part - the biggest problem with the 25man version is that the abominations don't work.
  50.  
  51. Several of my raidmates have confirmed that while you can click on the "abom bottle" on his table, they don't turn into the abom at all.
  52.  
  53. Instead, the abom is counted as a "minion" and has no skills, cannot be controlled, and the player is unable to move and eventually dies.
  54. This means the fight cannot be completed at all - since the boss casts slime puddles around the area - which the non-working abominations should have been able to handle.
  55. Ok so for this report it would take you a lot longer to test, you would need to go into the instance with a group and test the bug out for yourself. If you are un-able to do so move it to pending and wait for another to test it.
  56. When testing bugs you need to make sure you are looking at the issue from different sections. You need to test the bug on different characters, accounts, classes and races, as well as horde and alliance to make sure that this isn’t a bug for just one class.
  57. If you confirm a bug, and a developer finds out that it’s not a bug then you will be open to review if this keeps happening then we will take action.
  58. This is a lot of the information you will need to know. If you have any questions please speak to any of the staff members.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement