|
|||||||
![]() |
| Thread Tools | Display Modes |
|
|
#1 | ||||
![]() Join Date: Mar 2012
Reputation: 59
Posts: 272
|
Prioritize Bugs by Voting
You can prioritize issues and bugs to help Valve determine what fixes and features enhancements are important for the CS:GO Community at http://www.64bitvps.com/csgo Step 1: It is critical to post bugs in the Official Bug Reporting Thread Step 2: Make sure the issue has not already been reported at 64bitvps.com/csgo by using the Search feature. If it has not been reported at 64bitvps.com/csgo, you can log in via Steam and create a Ticket. Incomplete and Poorly Written Issues will be marked as Invalid by Editors, and others in the Community. Be thorough in your report. Step 3: Endorse your Ticket on Reddit, Twitter, Google+, Facebook, and elsewhere to spread awareness. FOLLOW THESE BUG WRITING GUIDELINES WHEN REPORTING ISSUES Writing Effective Bug Titles Writing Effective Titles for Issues Tickets for ADD/REMOVE/CHANGE Feature Requests This is the most important part of your report. Detailed titles get clicked on, your report will not get enough exposure if your title is of poor quality. If your title does not meet minimum editorial quality requirements, your report will be flagged as INVALID, and nobody will see your report. You will have to resubmit with a better title. Quote:
Quote:
Writing Effective Titles for Bugs Tickets which Report CRASHES/GLITCHES/EXPLOITS etc A Cause and Event format for the Title should be used when reporting Bugs which do not require the addition/removal/change of a Feature. Your Title should explain the problem, not your suggested solution.
Quote:
Quote:
Writing Precise Steps to Reproduce How can a developer reproduce the bug on his or her own computer? Steps and System Configurations to reproduce a bug/issue are the most important part of any report. If a developer at Valve is able to reproduce the conditions described in your ticket, the bug is likely to get serious developer attention. Describe Steps to Reproduce the Problem. State the intent of each step. Be precise.
Precisely describe your Expected or Desired Behavior. Clearly separate facts (observations) from your speculations.
Intermittent or Random Bugs Developers will want to be sure of whether they’re dealing with a true intermittent fault or a machine-specific fault. They will want to know lots of details about your computer, so they can work out how it differs from theirs. A lot of these details will depend on the particular program, but one thing you should definitely be ready to provide is version numbers. The version number of your Operating System, your Video Card Model Number and Driver Revision, and any other details about your computer which you think may be relevant to your issue (concurrently running programs, total system memory, etc). If other users also experience the same Intermittent or Random Bug, gathering a collection of system profiles in the Comments is extremely helpful for developers. Tags Tags are comma separated words, or groups of words, which allow bugs to get further categorized into subsets. If more than 1 bug can be categorized by a single label which does not exist in the “Category” drop down, you will want to specify that label as a “Tag”.
There is a community effort to organize bugs via the following hyperlinked tags:
Severity and Priority Priority is structured in two ways. Priority is determined both by the Severity categorization of a report, and the number of thumbs up votes a report gets. Priority by Votes Each person only gets one vote per report, and all votes are final. If you feel an issue should not be given developer attention now, refrain from voting. If you feel an issue should not be addressed at all, vote thumbs down. It is important to review every report and thumbs up vote everything that is a priority for you, including thumbs-upping your own reports. Priority by Severity Severity measures how much an Issue impacts the game
Last edited by FOBioPatel: 09-07-2012 at 05:38 PM. Reason: updated Bug Writing Guidelines |
||||
|
|
|
|
|
|
|
Valve
Join Date: Nov 2008
Reputation: 149
Posts: 265
|
This is a nice idea. It'll be interesting to see how this develops as you get more participation.
Good luck to you. |
|
|
|
|
|
#3 |
![]() Join Date: Nov 2008
Reputation: 19
Posts: 398
|
Good idea.
|
|
|
|
|
|
#4 |
![]() Join Date: Aug 2012
Reputation: 12
Posts: 28
|
Brilliant idea. Good to see a dev response supporting this too.
|
|
|
|
|
|
#5 |
![]() Join Date: Jun 2008
Reputation: 22
Posts: 541
|
Working on it, great idea.
(the website is a bit slow atm) |
|
|
|
|
|
#6 |
![]() Join Date: Mar 2012
Reputation: 59
Posts: 272
|
|
|
|
|
|
|
#7 |
![]() Join Date: Nov 2010
Reputation: 0
Posts: 11
|
bumpity bump
|
|
|
|
|
|
#8 |
![]() Join Date: Feb 2011
Reputation: 4
Posts: 196
|
great idea,need to spread the word to the community
|
|
|
|
|
|
#9 |
![]() Join Date: Nov 2008
Reputation: 19
Posts: 398
|
There is no "most important issues" visualization?
|
|
|
|
|
|
#10 |
![]() Join Date: Apr 2009
Reputation: 36
Posts: 208
|
thumbs up....
|
|
|
|
|
|
#11 |
![]() Join Date: Mar 2012
Reputation: 59
Posts: 272
|
People would jump on the most popular ones and ignore potentially very important ones which haven't yet been discovered. Such a view would be counterproductive to getting all the issues known and rated by the whole community.
For what it's worth: Valve can see everything, even though you can't. Last edited by FOBioPatel: 08-29-2012 at 04:16 PM. |
|
|
|
|
|
#12 |
![]() Join Date: Aug 2012
Reputation: 31
Posts: 231
|
I can't login :derp:
Can anybody report the reload delay? It's really annoying when the animation is done but you still wait like 1 second till you have a full clip again. |
|
|
|
|
|
#13 |
![]() Join Date: Aug 2010
Reputation: 301
Posts: 2,201
|
+111111111111111111
Great site! |
|
|
|
|
|
#14 | |
![]() Join Date: Jun 2008
Reputation: 22
Posts: 541
|
Quote:
I have to agree : at least Valve should able to see what bugs and issues have been prioritized. Or even us : i don't see people rating stuff on page 11 and so on. Last edited by FreIHh.: 08-29-2012 at 04:04 PM. |
|
|
|
|
![]() |
|
||||||
| Thread Tools | |
| Display Modes | |
|
|