| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Sofitia Mourtos
   |
Posted - 2004.07.28 12:55:00 -
[1]
Simple question: what is the official/correct way of reporting a bug ?
Afaik Redundancy have been reworking the whole bug-reporting/tracking system, but so far that is only internaly at ccp (?).
Lets say that I found a bug, I am able to reproduce it by a exact sequence of operations, it might only be a small bug but a bug never the less..
1: how do I check if the bug is know ?
2: where/how do I report the bug (includeing reproducable senario / log-files / attached images / whatever)
3: where/how can I track the status of the bug I have reported (so that I dont feel like I'm just wasteing time writing bug-reports to /dev/null )
Ofcourse there is this forum, but that hardly solves problems posting here. There Used to be a petetion/bug-report option not sure it is there anymore and afaik I dont know where to "track" my bug once it is there...
----------------------------------------
Buying Co-processor II bpo |
Sofitia Mourtos
|
Posted - 2004.07.28 12:55:00 -
[2]
Simple question: what is the official/correct way of reporting a bug ?
Afaik Redundancy have been reworking the whole bug-reporting/tracking system, but so far that is only internaly at ccp (?).
Lets say that I found a bug, I am able to reproduce it by a exact sequence of operations, it might only be a small bug but a bug never the less..
1: how do I check if the bug is know ?
2: where/how do I report the bug (includeing reproducable senario / log-files / attached images / whatever)
3: where/how can I track the status of the bug I have reported (so that I dont feel like I'm just wasteing time writing bug-reports to /dev/null )
Ofcourse there is this forum, but that hardly solves problems posting here. There Used to be a petetion/bug-report option not sure it is there anymore and afaik I dont know where to "track" my bug once it is there...
----------------------------------------
Buying Co-processor II bpo |
Sofitia Mourtos
|
Posted - 2004.07.28 12:57:00 -
[3]
Hmm and I thought I did check the sticky topics first :-)..
Guess I'll just read the top one
----------------------------------------
Buying Co-processor II bpo |
Sofitia Mourtos
|
Posted - 2004.07.28 12:57:00 -
[4]
Hmm and I thought I did check the sticky topics first :-)..
Guess I'll just read the top one
----------------------------------------
Buying Co-processor II bpo |
Sofitia Mourtos
|
Posted - 2004.07.28 13:02:00 -
[5]
Still that only answers question nr 2..
I'm still in doubt where to check if the bug is know, and where to track my bug (e.g. rejected (not a bug after all), accepted (was a bug addet to the bug-list), fixed (bug fixed will be released in a upcomming patch if not sooner))
----------------------------------------
Buying Co-processor II bpo |
Sofitia Mourtos
|
Posted - 2004.07.28 13:02:00 -
[6]
Still that only answers question nr 2..
I'm still in doubt where to check if the bug is know, and where to track my bug (e.g. rejected (not a bug after all), accepted (was a bug addet to the bug-list), fixed (bug fixed will be released in a upcomming patch if not sooner))
----------------------------------------
Buying Co-processor II bpo |
Feral
|
Posted - 2004.07.28 13:15:00 -
[7]
In answer to your questions: feedback is extremely rarely given, and only in highly unusual cases, and the bug reporting page can be found on the Eve-insider submenu. (Or Here)
|
Feral
|
Posted - 2004.07.28 13:15:00 -
[8]
In answer to your questions: feedback is extremely rarely given, and only in highly unusual cases, and the bug reporting page can be found on the Eve-insider submenu. (Or Here)
|
Redundancy
|
Posted - 2004.07.28 13:19:00 -
[9]
So far, there's no changes to the player pages for bug reporting other than providing more information on how to submit a good bug report.
|
Redundancy
|
Posted - 2004.07.28 13:19:00 -
[10]
So far, there's no changes to the player pages for bug reporting other than providing more information on how to submit a good bug report.
|
Sofitia Mourtos
|
Posted - 2004.07.28 13:58:00 -
[11]
 Originally by: Redundancy
So far, there's no changes to the player pages for bug reporting other than providing more information on how to submit a good bug report.
Just so that I understand this 100%..
It is expected (so far) that we use time writing up good bug-reports (not talking about the "hey this dont work" types), for bugs that most likely already are known ? (aka wasting our time)
Or is there a place to search for existing bugs ? (I remember there was one during beta).
----------------------------------------
Buying Co-processor II bpo |
Sofitia Mourtos
|
Posted - 2004.07.28 13:58:00 -
[12]
Originally by: Redundancy
So far, there's no changes to the player pages for bug reporting other than providing more information on how to submit a good bug report.
Just so that I understand this 100%..
It is expected (so far) that we use time writing up good bug-reports (not talking about the "hey this dont work" types), for bugs that most likely already are known ? (aka wasting our time)
Or is there a place to search for existing bugs ? (I remember there was one during beta).
----------------------------------------
Buying Co-processor II bpo |
Redundancy
|
Posted - 2004.07.28 14:30:00 -
[13]
Originally by: Sofitia Mourtos
It is expected (so far) that we use time writing up good bug-reports (not talking about the "hey this dont work" types), for bugs that most likely already are known ? (aka wasting our time)
This is one of the reasons I'm hesitant to do it. Every time I hear people talking about this, it's from the point of view of looking for a list of things and deciding not to report anything that's already listed. We get far too few good reports on many problems in the first place, and sometimes need more than one report to get a full picture, so it would appear that putting up a list of stuff that we know about and are looking into is only going to reduce the information we'd get.
|
Redundancy
|
Posted - 2004.07.28 14:30:00 -
[14]
Originally by: Sofitia Mourtos
It is expected (so far) that we use time writing up good bug-reports (not talking about the "hey this dont work" types), for bugs that most likely already are known ? (aka wasting our time)
This is one of the reasons I'm hesitant to do it. Every time I hear people talking about this, it's from the point of view of looking for a list of things and deciding not to report anything that's already listed. We get far too few good reports on many problems in the first place, and sometimes need more than one report to get a full picture, so it would appear that putting up a list of stuff that we know about and are looking into is only going to reduce the information we'd get.
|
Sofitia Mourtos
|
Posted - 2004.07.28 15:14:00 -
[15]
Ok I can understand the fact that a bug might result in defects in several areas, and that what might be reproduceable for one person might not be for another (due to a fact not includet in the description).. fair enough..
That could partly be solved by haveing a few states on each bug e.g:
Fixed - deployed
Fixed - not deployed (comming in next patch)
Open - Identified (no more reports needet)
Open - not identified (send more reports since we cant find/reproduce this)
This way we would know if we could do anything to help (and if all we can do is wait -> the open-identified status)
My main point is that currently I dont report bugs, I often find some... However I would much rather use my time playing eve than filling out bug-reports...
As customers I dont see that it is our responsobility to locate the bugs, but if we do and want them fixed we should have the posibility to "speedup the process" by helping out with identifying/reporting the bug, for that purpose we need to be able to evaluate if it is worth use the time for it.
(if it is known already)..
The motivation to report bugs could be increased if we got some kind of feedback on the reports that are acutaly sent, e.g. a eve-mail/e-mail saying "we got your bug-report and it was usefull" or "we got your bug-report but we need more detailed information to locate the bug"..
All in all I'm looking for more feedback on any effort beeing made by the playerbase in reporting bugs...
(do we get such a mail atm ?)
----------------------------------------
Buying Co-processor II bpo |
Sofitia Mourtos
|
Posted - 2004.07.28 15:14:00 -
[16]
Ok I can understand the fact that a bug might result in defects in several areas, and that what might be reproduceable for one person might not be for another (due to a fact not includet in the description).. fair enough..
That could partly be solved by haveing a few states on each bug e.g:
Fixed - deployed
Fixed - not deployed (comming in next patch)
Open - Identified (no more reports needet)
Open - not identified (send more reports since we cant find/reproduce this)
This way we would know if we could do anything to help (and if all we can do is wait -> the open-identified status)
My main point is that currently I dont report bugs, I often find some... However I would much rather use my time playing eve than filling out bug-reports...
As customers I dont see that it is our responsobility to locate the bugs, but if we do and want them fixed we should have the posibility to "speedup the process" by helping out with identifying/reporting the bug, for that purpose we need to be able to evaluate if it is worth use the time for it.
(if it is known already)..
The motivation to report bugs could be increased if we got some kind of feedback on the reports that are acutaly sent, e.g. a eve-mail/e-mail saying "we got your bug-report and it was usefull" or "we got your bug-report but we need more detailed information to locate the bug"..
All in all I'm looking for more feedback on any effort beeing made by the playerbase in reporting bugs...
(do we get such a mail atm ?)
----------------------------------------
Buying Co-processor II bpo |
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |