|
Author |
Thread Statistics | Show CCP posts - 28 post(s) |
|
CCP Phantom
C C P C C P Alliance
4593
|
Posted - 2014.08.19 16:17:00 -
[1] - Quote
The EVE Community is a group of incredibly skilled and passionate individuals as proven over and and over again (some joining the ISD volunteer program). Pointing out bugs, reporting them to our developers and supporting the dev teams with information and logs shows how skilled and passionate you are.
With the introduction of the new bug reporting system a while ago, two vital things were still missing: the ability to communicate between you and the developers/volunteers and the ability to see and edit your bug report.
CCP Goliath brings good news that you now can communicate with the developers/volunteers (and the developers/volunteers with you) and that you can edit your bug report.
To learn more about all the improvements to bug reporting check out CCP Goliath's latest blog An Update on Bug Reporting, Part 3! CCP Phantom - Senior Community Representative - Volunteer Manager |
|
|
CCP Phantom
C C P C C P Alliance
4593
|
Posted - 2014.08.19 16:18:00 -
[2] - Quote
Retar Aveymone wrote:I found a bug: Quote: Can't find item Sorry, we could not find the item you were looking for.
This has been fixed now, thank you for reporting this bug! CCP Phantom - Senior Community Representative - Volunteer Manager |
|
|
CCP Goliath
C C P C C P Alliance
2356
|
Posted - 2014.08.19 16:20:00 -
[3] - Quote
Looking forward to discussing any feedback you lovely people have! Stay classy though CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Lebowski
C C P C C P Alliance
182
|
Posted - 2014.08.19 16:49:00 -
[4] - Quote
QA Dev Blog FTW!
Massive thanks to all you folks who submit bug reports, you guys rock! I cant tell you how great it will be to be able to have direct communication with you all now CCP Lebowski | EVE Quality Assurance | Team Five-0
https://twitter.com/ccp_lebowski |
|
|
CCP Goliath
C C P C C P Alliance
2358
|
Posted - 2014.08.19 16:56:00 -
[5] - Quote
ArmEagle Kusoni wrote:Nice improvement there.
Though for my few reports - oldest one is from 2014/03/23 - none of the following communication from CCP or myself can be found there. Will the comments section be filled with the 'chat history' (from both sides) starting now. Or is that a later improvement?
It''s from now, and you will only be able to see comments that have been explicitly tagged as being publically viewable. Internal comments will still be internal. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2358
|
Posted - 2014.08.19 17:00:00 -
[6] - Quote
Gilbaron wrote:i really like the idea of a system that would allow us to priorize your work :)
there are some bugs out there, older than the internet that annoy us every now and then, it would be great to have a way to bring them to CCPs attention
Thanks for the feedback! We can always make our best guesses (backed with data ofc) as to what legacy fixes people do and don't care about, but getting some extra, invested, eyes on it could be really interesting. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2358
|
Posted - 2014.08.19 17:04:00 -
[7] - Quote
Kusum Fawn wrote:Any word on when you guys will be publishing lists of intended features and intended behavior changes ? The vast majority of things that I see as bugs are apparently working as intended initially and later revealed to be bugs/exploits. Having a list somewhere that you guys actually make public and/or keep updated for things being worked on would go a longer way to help reporting then updating the graphics behind the bug reporting system
I'm not 100% sure I follow what you mean... When you say "lists of intended features", do you mean like the "Coming In Hyperion" blog that Seagull wrote last week, or something different?
Kusum Fawn wrote: Something like this would also be incredibly useful as a way to promote things that are important to the general eve community (and not just the small vocal minority who work with POS) however your (CCP as a whole) general refusal to listen to Sisi feedback makes me believe that things which are defects but somehow seen as feature requests (Tool Tips sliders, Industry UI inputs list vs graphics display) will simply be ignored yet again in another format despite them not working as intended.
Thanks very much for telling us how you feel. Sorry that you don't think we take Sisi feedback on board, but I assure you the teams are as diligent as possible when it comes to reading the threads and discussing the ideas in them! That being said, the items in the hypothetical list would already have been acknowledged by us to be issues, so does that go some way to mitigating your concerns? CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2358
|
Posted - 2014.08.19 17:05:00 -
[8] - Quote
Green Gambit wrote:Regards to voting up bugs/features... Something like Ideastorm would be cool, where the community can suggest ideas and all subscribed accounts get to up-vote their favourite three ideas (can change your votes at any time etc) would be pretty cool. It would certainly be a good way for you to get a good impression of what areas are important to the player-base. The same tool could be used for F&I suggestions, bugs, "little things" etc separately. http://www.ideastorm.com/
Thanks for the link! Will check it out later and let you know my impressions! CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
ISD Ezwal
ISD Community Communications Liaisons
1944
|
Posted - 2014.08.19 17:29:00 -
[9] - Quote
the Dev Blog wrote: First, a unique ID key. Styled as EBR-XXXX, this is the number of your bug report in our database, and the first thing you should refer to when discussing a bug report with a developer. Feel free to reference it in forum posts, tweets, and EVEmails or in discussions about the test server (Singularity/GÇ¥SisiGÇ¥) or live server (Tranquility/GÇ¥TQGÇ¥) Eh....I hate to spoil te fun, but in general talking about bug reports on this forum is prohibited as talking about the reports itself inevitably leads to talking about the bug itself..... The exceptions being if a Dev/GM specifically asks for it and threads in the Test Server Feedback section.
15. Posting about bugs and exploits is prohibited.
Bugs and exploits should be reported through the proper channels. Bugs should be brought to the attention of CCP by filing a bug report for our Quality Assurance department. More information on filing bug reports can be found here. Discussions about unverified issues in game can cause unnecessary panic in the community. When there is an issue that the EVE Online community needs to be aware of, it will be communicated via an official statement from CCP after thorough investigation. ISD Ezwal Captain Community Communication Liaisons (CCLs) Interstellar Services Department |
|
|
CCP Explorer
C C P C C P Alliance
2315
|
Posted - 2014.08.19 18:14:00 -
[10] - Quote
I hope these improvements to the bug reporting website help you in helping us improving EVE Online; I, for one, like them.
I would like to emphasize a part of the devblog that we still strongly prefer that bug reports be submitted through the in-client bug reporting tool (accessed via the Help menu). It automatically attaches things like logs and also allows you to take screenshots, annotate them, and upload them along with your report. Your submissons from the client will appear on the My Bug Reports page on the website and will be equally interactive. Erlendur S. Thorsteinsson | Senior Development Director | EVE Online // CCP Games | @erlendur |
|
|
|
CCP Goliath
C C P C C P Alliance
2362
|
Posted - 2014.08.19 20:10:00 -
[11] - Quote
Nicen Jehr wrote:Why don't you have a Closed resolution, "Fixed" ?
Also, I would use a public bug tracker where I could vote on priorities. But I'd extend it to be feature requests too. And add tags, like 'little thing', this way you wouldn't have to go through the huge hassle of "post little things in thread, parse posts into machine readable format, have CSM put up a voting app", and new suggestions would be immediately votable.
Bug reports don't get "fixed" per se - they either become or are attached to defects, which are fixed, but there is no way currently to relay the state of the defect to the bug report attached to it. Going back over old bug reports to set them to fixed would be very time consuming.
When you say extend the public bug tracker idea to feature requests, do you mean that you would vote on features that we have proposed, or that you would submit features of your own? We already have a place for the latter - in case you aren't aware, it's the Features and Ideas forum.
Tags are great and also come built into Jira. Making them searchable could be good, but making them enterable might not be so good (see Marco Reus and the latest Puma twitter campaign for an example of how that doesn't always work as intended). Definitely a good idea though - thanks for your input!
EDIT: Some guests just came round with CCP Lebowski, so will be answering more posts tomorrow morning! Keep the chat going! CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Habakuk
C C P C C P Alliance
973
|
Posted - 2014.08.19 21:40:00 -
[12] - Quote
Tvashnar Crendraven wrote:CCP Goliath wrote:
Bug reports don't get "fixed" per se - they either become or are attached to defects, which are fixed, but there is no way currently to relay the state of the defect to the bug report attached to it. Going back over old bug reports to set them to fixed would be very time consuming.
No doubt. Bugs have costs, and those costs are higher if you ship them to customers. "'Closed" does not tell me whether I should not be seeing the issue anymore; or whether my understanding is broken and it is not actually a bug or any number of other things which might make me feel that the time I spent to file the bug was not wasted. Simply closing the issue without comment or a tag like 'fixed', 'not-repro', 'by design' or even 'raised a bug in our real bug tracking system' means that this nice new interface into our bug reports is *useless*.
Regarding bugs in "Attached" state: Regardless on what is being shown, you will only know for sure (well in some cases not even then...) that your bug is fixed on TQ, when it will be mentioned in the patch notes (nearly all player-facing bug fixes are mentioned in the patch notes, with the exception of most exploits and some very small issues like spelling fixes). Even if we would show the internal status of the real defect on your bug report it would still cause confusion, as you do not know, when the fix will reach TQ (in some cases this will be the next day, but in some cases it can take a few months (depending in which context it is being fixed) - and no, even the internal information is not as clear.
Regarding bugs in "Closed" state: Old bug reports are unfortunately lacking any further information. I hope that In the future you will often see comments on why a bug report was closed or you will see bug reports with the status "Need more info" with details on what we need. I had a short check at our stats and most bug reports in the "Closed" state were closed because the report was somehow incomplete and the next category are bugs, which were not reproducible. Both cases should improve alot, if we are able to get further information from the reporter. We are unfortunately still not able to send you an email if we need further information, but we are getting closer. We want for sure to give you as much information as easily possible on why your bug report was closed, but we don't know yet on how this will look like exactly when everything is in place.
CCP Habakuk | EVE Quality Assurance | Team Gridlock-á Bug reporting | Mass Testing |
|
|
CCP Habakuk
C C P C C P Alliance
973
|
Posted - 2014.08.19 21:41:00 -
[13] - Quote
Vincent Athena wrote:... Also the status "closed" is just not informative enough. If something has "insufficient information", I would like to know, so I can try explaining it again. If it cannot be reproduced, I would like to try again, maybe with some other method for repro that might work for you. If its "working as intended" I would like to know so I can do a feature request in F & I.
I totally agree and we will be working on improving this. CCP Habakuk | EVE Quality Assurance | Team Gridlock-á Bug reporting | Mass Testing |
|
|
CCP Habakuk
C C P C C P Alliance
978
|
Posted - 2014.08.19 22:23:00 -
[14] - Quote
Hoshi wrote:I made a bug report about a month ago about inconsistent use of Agility/Inertia in module descriptions. But the my bug reports page says "You have not submitted any bug reports." (and yes I have checked all account to make sure I didn't submit it on another). Does this mean that there where some error and the bug report never actually reached CCP?. Do I need to resubmit the report?
I am also not able to find a bug report about this in your given time frame. The issue itself is known and there is an open defect for it, so there is no need to file a new bug report about it. CCP Habakuk | EVE Quality Assurance | Team Gridlock-á Bug reporting | Mass Testing |
|
|
CCP Habakuk
C C P C C P Alliance
979
|
Posted - 2014.08.19 23:31:00 -
[15] - Quote
asteroidjas wrote:i am currently not able to submit a bug report, as it keeps saying i need to 'fill out all fields' yet gives me no options to select in the 'category' drop-down.
Hmmm, this is from the client on Tranquility or where do you see this problem? I just tried it and for me it worked fine. It would be helpful if you could get logs from logserver (more info can be found on in the bug reporting page, which is linked in my signature) and create a bug report through the web site. CCP Habakuk | EVE Quality Assurance | Team Gridlock-á Bug reporting | Mass Testing |
|
|
CCP Habakuk
C C P C C P Alliance
980
|
Posted - 2014.08.20 00:54:00 -
[16] - Quote
Noriko Mai wrote:To be honnest, I stopped writing new reports because I thought no one looks into it. After a few months I could not remember what my report was about, just that I've written one. I just checked my bugreports and most of them are attechend to a defect. So someone actually looked at it and something may/will happen. It's is so satisfying. (No joke or sarcasm) *hugs* will write bugreports again. Sorry for not believing EDIT: I just checked all of them and some are fixed or never made it from SiSi to TQ.
- EBR-15230 is fixed.
- EBR-16144 is fixed.
- EBR-16465 is fixed.
- EBR-19126 is fixed.
So if I'm not mistaken or my reports are only a small part of a bigger defect, all of them can be closed.
I had a short look and it seems like all four of those got fixed because of your bug reports. Thank you!
CCP Habakuk | EVE Quality Assurance | Team Gridlock-á Bug reporting | Mass Testing |
|
|
CCP Habakuk
C C P C C P Alliance
980
|
Posted - 2014.08.20 01:17:00 -
[17] - Quote
Kenneth Feld wrote:I submitted a bug in Dec 2013, never heard a thing about it, kinda gave up on bug reports
Looks today and find out nothing has been touched on it. Although i re submitted it on a separate pilot.
23 accounts and 41 pilots, anyway, we could make it so you can see all your bug reports in one area. i found several duplicates today as well, that i didn't even remember writing
Also, added 7 more that i had been putting off writing cause well, not getting feedback kinda leads you to believe no one knows or cares, although seeing one untouched for 9 months kinda does the same thing...
Yeah, unfortunately we were not successful in being able to process all bug reports within the last year and we did not decide to mass-close the remaining ones (which might have looked better). If you find a very old bug report not closed and you have additional info to it - or you found out that it was not a bug: Please add a comment to it. I'll try to go through bug reports which were updated and see if I can do anything with them.
Btw, some background info: The main part of the bug reports are processed by our volunteer bug hunters and smaller parts are done by us in QA and by our testing partner. Due to several reasons (including the signup being closed for a long time due to technical difficulties) we had less active bug hunters than in previous years - this had quite some impact on our ability to process bug reports. In the last few months the situation improved a lot due to several new and some very active bug hunters (Thanks go especially to BH Nonlocality) - but we could need several additional volunteers. Follow the links in the top post, if you are interested in helping as bug hunter. CCP Habakuk | EVE Quality Assurance | Team Gridlock-á Bug reporting | Mass Testing |
|
|
CCP Goliath
C C P C C P Alliance
2364
|
Posted - 2014.08.20 10:12:00 -
[18] - Quote
David Laurentson wrote:CCP Goliath wrote: Thanks very much for telling us how you feel. Sorry that you don't think we take Sisi feedback on board, but I assure you the teams are as diligent as possible when it comes to reading the threads and discussing the ideas in them! That being said, the items in the hypothetical list would already have been acknowledged by us to be issues, so does that go some way to mitigating your concerns?
I think his concern is that those issues were acknowledged when they hit TQ, and closed in error on SiSi. Not ignored in threads, Bug Reports were raised, and closed, despite them actually being bugs. Do you do any investigation of TQ-impacting bugs to see if they were raised on SiSi, and how they were handled? If not, it might be worthwhile: you might have some internal communication work to do, or need to change how you set targets (I can only guess, not working at CCP!).
This might be to do with our version control then. Some bugs will be closed while still being a problem on TQ, because we have verified that the fix works on one of our test environments (Sisi is one, but there are many others)
We do perform RCA (root cause analysis) on certain escaped issues (escaped describes the defect "escaping" from the test environment into the live environment). This is usually facilitated by me, with the involved team(s), and we just go over how the defect managed to get to TQ, strictly looking at the facts and leaving any blame or recrimination out of the picture (one of the worst things you can do, especially in QA, is create an environment where failure has massive negative consequences so that people become afraid of it - that's how problems stay hidden instead of being discussed and solved). Once we know how it happened, we work out what lessons we can take from this so as to not have it happen again, and usually make sure we have a test case or two in our regression suite to cover the defect and areas around it.
Having hard targets with defects is a very double edged sword - some targets are positive, such as "no A or B class bugs on release", others are impossible and dangerous, such as "0 bugs for every feature" or "a good QA should find X bugs per day". CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2364
|
Posted - 2014.08.20 10:13:00 -
[19] - Quote
Che Biko wrote:CCP Goliath wrote:Additionally, editing a bug once it has been attached or closed will be futile, as we will no longer be checking that report. Then why not remove the edit option/button for those reports People may not know about the futility, and think "The button/option is still there, so it must serve a purpose."
We likely will in the next iteration, just didn't have time before Tier went on summer vacation CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2364
|
Posted - 2014.08.20 10:18:00 -
[20] - Quote
Tvashnar Crendraven wrote:CCP Goliath wrote:
Bug reports don't get "fixed" per se - they either become or are attached to defects, which are fixed, but there is no way currently to relay the state of the defect to the bug report attached to it. Going back over old bug reports to set them to fixed would be very time consuming.
No doubt. Bugs have costs, and those costs are higher if you ship them to customers. "'Closed" does not tell me whether I should not be seeing the issue anymore; or whether my understanding is broken and it is not actually a bug or any number of other things which might make me feel that the time I spent to file the bug was not wasted. Simply closing the issue without comment or a tag like 'fixed', 'not-repro', 'by design' or even 'raised a bug in our real bug tracking system' means that this nice new interface into our bug reports is *useless*.
This seems to be a common sentiment, and we will discuss it internally and see if adding the resolution field (which would show you the Closed resolution, but wouldn't provide any details on fixes, for reasons I've explained in other posts) is something we can fit in to the next iteration. "Attached" means "Raised a bug in our real bug tracking system", relatively speaking. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
|
CCP Goliath
C C P C C P Alliance
2364
|
Posted - 2014.08.20 10:19:00 -
[21] - Quote
Circumstantial Evidence wrote:CCP Goliath wrote:Bug reports don't get "fixed" per se - they either become or are attached to defects, which are fixed, but there is no way currently to relay the state of the defect to the bug report attached to it. Going back over old bug reports to set them to fixed would be very time consuming. Please work on automating this :) I have bugs both attached / "I-know-fixed", and attached / "I-don't-know-anything". I would like to see a column with a one word report / state of the internally-written defect our bug is attached to.
Impossible without rewriting part of our Jira instance I believe. This isn't a desired solution as it makes plugin maintenance and ongoing support much more complex and risky. Sorry, but at least for now this isn't going to happen. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2364
|
Posted - 2014.08.20 10:24:00 -
[22] - Quote
Vincent Athena wrote:I like the idea of being able to vote on legacy bugs. But, if you have no way of setting a bug to at status of "fixed" how will this list be populated? You will not know which bugs to include in the list as not a single one will have any indication that it has been fixed!
I would think that if a bug can be attached to a defect, then when that defect has been fixed, that information could automatically flow back to the bug report.
Also the status "closed" is just not informative enough. If something has "insufficient information", I would like to know, so I can try explaining it again. If it cannot be reproduced, I would like to try again, maybe with some other method for repro that might work for you. If its "working as intended" I would like to know so I can do a feature request in F & I.
The legacy bugs would be in our database, so would have resolutions, and obviously we can see when defects are fixed - the thing here is that defects are invisible to you, and what you see are called bug reports. The jargon is pretty important when discussing both at the same time to differentiate.
Unfortunately the defect tracking software doesn't work like you describe with the flow of issues, at least at this time, but it does get worked on continually by Atlassian, so who knows what the future may bring!
CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2364
|
Posted - 2014.08.20 10:31:00 -
[23] - Quote
Rionan Nafee wrote:Thank you for your improvements and the infos about them.
One suggestion:
How would it be if the Bug Hunters/Dev Teams can "rate" the bug reports and give comments about the quality of the submitted bug reports?
So players can see how usefull their reports were and how they can improve their next ones therefore the neverending work of the Bug Hunters and Devs can be make easier.
This is something that's come up in our meetings before. On the one hand, as you say it's great to give people positive feedback when they submit a report that leads to us fixing or discovering an issue. On the other hand, the maintenance around such a system (you'd need rules, and checks, and consistency, etc) as well as the work that would have to go into creating it, might be a little much, or the wrong effort in the wrong place... It's definitely not entirely ruled out, but right now I don't have a good idea of how it would work well either. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2365
|
Posted - 2014.08.20 16:44:00 -
[24] - Quote
Rionan Nafee wrote:CCP Goliath wrote:Rionan Nafee wrote:Thank you for your improvements and the infos about them.
One suggestion:
How would it be if the Bug Hunters/Dev Teams can "rate" the bug reports and give comments about the quality of the submitted bug reports?
So players can see how usefull their reports were and how they can improve their next ones therefore the neverending work of the Bug Hunters and Devs can be make easier. This is something that's come up in our meetings before. On the one hand, as you say it's great to give people positive feedback when they submit a report that leads to us fixing or discovering an issue. On the other hand, the maintenance around such a system (you'd need rules, and checks, and consistency, etc) as well as the work that would have to go into creating it, might be a little much, or the wrong effort in the wrong place... It's definitely not entirely ruled out, but right now I don't have a good idea of how it would work well either. Thank you for this information. Is there any other way possible to know if the submitted bug reports are usefull or only a pain in the ass for the bug hunters?
At this time there definitely isn't an easy way to relay that info back to you, barring commenting "great report" or similar on the report, which will absolutely have to be left up to the individuals processing the reports (but will be encouraged) CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2367
|
Posted - 2014.08.22 09:50:00 -
[25] - Quote
Kenneth Feld wrote:well, I got my bug report "Attached" but attached to what? EBR-22458 What is going to get done?
The bug report is kinda one of those it used to be this way, now it is that way...
Attached doesn't tell me if the old way is correct or the new way is correct.....
How the heck am i supposed to know whether to shut up and wait 6 years for it to revert to the old way or 4 years for it to be fixed the new way?
At this rate, going back to old style forum whining is still the best answer......
Attached means that it has either had a defect created from it, or attached to an existing defect we already had. This is basically the best outcome of a bug report. As I've explained further up the thread, there is no way for us to currently relay the status of defects that bug reports are attached to, to you. In the case of this issue, you filed it on the 19th August, we processed it on the 21st and CCP Claymore made a defect from it. That defect is now assigned to a developer and waiting to be fixed (note, I do not know the nature of the intended fix). If the report was invalid, it would show as Closed rather than Attached. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2368
|
Posted - 2014.08.25 10:19:00 -
[26] - Quote
Nicen Jehr wrote:CCP Goliath wrote:When you say extend the public bug tracker idea to feature requests, do you mean that you would vote on features that we have proposed, or that you would submit features of your own? We already have a place for the latter - in case you aren't aware, it's the Features and Ideas forum. I'm proposing automating both. Right now, to get an idea to CCP karkur and CCP Punkturis they have to read the Little Things thread and notice the post and presumably make a note in your internal to-do list tracking. I propose instead a features and suggestions app where pilots use SSO to prove identity and can post specific ideas. If you want to keep discussion on the forums then you could programatically make a features and suggestions thread for each post. But the goal is for me to post 100 little things, and have other pilots upvote the 10 most desired ideas, so your devs don't have to sort through the less-desired 90.
It's an interesting notion for sure. Out of my remit, but will definitely pass it on to others. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2368
|
Posted - 2014.08.25 12:28:00 -
[27] - Quote
Nicen Jehr wrote:CCP Goliath wrote:When you say extend the public bug tracker idea to feature requests, do you mean that you would vote on features that we have proposed, or that you would submit features of your own? We already have a place for the latter - in case you aren't aware, it's the Features and Ideas forum. I'm proposing automating both. Right now, to get an idea to CCP karkur and CCP Punkturis they have to read the Little Things thread and notice the post and presumably make a note in your internal to-do list tracking. I propose instead a features and suggestions app where pilots use SSO to prove identity and can post specific ideas. If you want to keep discussion on the forums then you could programatically make a features and suggestions thread for each post. But the goal is for me to post 100 little things, and have other pilots upvote the 10 most desired ideas, so your devs don't have to sort through the less-desired 90.
Sorry for the double post, but I just found this: https://www.fuzzwork.co.uk/things/
Seems like the CSM are using something similar to what you describe to collate these things. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
CCP Goliath
C C P C C P Alliance
2373
|
Posted - 2014.08.29 14:57:00 -
[28] - Quote
Kusum Fawn wrote: But really having a known issues list which is updated regularly with sections for "This is not fixed yet" and "This is fixed" would go a long way to reducing the number of similar bug reports of varying detail that you receive and allow you to focus closer on the repeating issue(s) that people are still seeing. Allowing us (the players) to indicate on someone else's bug report that we are also observing the same issue will allow you to see the most common issues faster.
Yeah! I would really hope that one of the outcomes of such a system would be a reduction in redundancy, replaced with a "me too" button or similar. You're entirely correct of course that it would allow us to process more issues, and focus directly on other more difficult issues. CCP Goliath | QA Director | EVE Illuminati | @CCP_Goliath |
|
|
|
|