z0ttel
06-26-2011, 10:25 AM
Hello everybody,
I know that this topic has already been discussed in the past but I think it still gets more and more important which each (BETA)-patch we get.
Currently all issues, flaws, requests for improvement reported by the community are spread over several threads and subthreads. Sometimes, there are up to four different threads used for reporting for one single game version (announcement thread, BETA-thread, final release thread and the remarkable Insuber's thread).
This leads to the situation, that valuable information is stored inside this forum, but it's very hard (nearly impossible in some cases) to find. I assume that even for 1C it's hard to maintain the overview of all reported issues with all the related details, which could explain the *ehm* interesting choice of some bug fixes ;)
So my idea is to re-think about the implementation of a *real* issue tracking system like Bugzilla, Mantis, ... (http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems).
The benefit would be that all items reported by the user would be stored in one single data base. For each report a set of mandatory data could be defined which must be entered by the user (game version, system specs, category (FM, DM, ...). Because all this stuff is stored in one data base, searching for already reported items would become very easy - most of the issue trackers are able to accept user-defined queries to search for specific items (e.g. "all FM-related issues since version 1.01.000").
As far as I remember there was no response from 1C if they would like to setup/participate in such an issue-tracking system, but even if they decide not to participate, that system would nevertheless be a great improvement to our current situation.
Being a software-developer myself, all I can say is that I would have gone nuts already several years ago if we wouldn't have used such a system in our company.
Maybe it's possible to use the issue tracking systems provided by the big project hosting sites like sourceforge?
What do you think?
I know that this topic has already been discussed in the past but I think it still gets more and more important which each (BETA)-patch we get.
Currently all issues, flaws, requests for improvement reported by the community are spread over several threads and subthreads. Sometimes, there are up to four different threads used for reporting for one single game version (announcement thread, BETA-thread, final release thread and the remarkable Insuber's thread).
This leads to the situation, that valuable information is stored inside this forum, but it's very hard (nearly impossible in some cases) to find. I assume that even for 1C it's hard to maintain the overview of all reported issues with all the related details, which could explain the *ehm* interesting choice of some bug fixes ;)
So my idea is to re-think about the implementation of a *real* issue tracking system like Bugzilla, Mantis, ... (http://en.wikipedia.org/wiki/Comparison_of_issue_tracking_systems).
The benefit would be that all items reported by the user would be stored in one single data base. For each report a set of mandatory data could be defined which must be entered by the user (game version, system specs, category (FM, DM, ...). Because all this stuff is stored in one data base, searching for already reported items would become very easy - most of the issue trackers are able to accept user-defined queries to search for specific items (e.g. "all FM-related issues since version 1.01.000").
As far as I remember there was no response from 1C if they would like to setup/participate in such an issue-tracking system, but even if they decide not to participate, that system would nevertheless be a great improvement to our current situation.
Being a software-developer myself, all I can say is that I would have gone nuts already several years ago if we wouldn't have used such a system in our company.
Maybe it's possible to use the issue tracking systems provided by the big project hosting sites like sourceforge?
What do you think?