Public Bugtracker [A How To Report Bugs]
Posted: Tue Jun 16, 2020 8:22 am
Hey guys and gals,
today we're going to be showing off our new public bugtracker starting with the following projects:
FS22 Basegame
all released DLCs so far
This is something we've been working on getting out there and want to finally start utilizing with gathering your bugs regarding our product(s).
What is this new "Public Bugtracker"?
It's a bug-tracking database we came up with for you, the players. Playing the latest DLC and found a bug you want to report? You can now finally do that in an orderly fashion directly after signing up:
https://feedback.giants-software.com/
We wanted to get away from the forum where these bugs would often get lost in the fray and won't find their way to the according developer (team). With our new bugtracker we can better handle the way you can report any findings you might discover while playing. The bugs can then be assigned properly to the according dev, similar to how our internal QA does. We can also let you know once a bug has been assigned or closed this way with just a few clicks.
What we hope to achieve is a clean environment in which bugs can be reported by anyone, filtered by our QA and taken care of or closed accordingly with a great overview of the whole process.
IMPORTANT: All bugs should be reported in ENGLISH language since that's what most of us devs communicate in here @GIANTS. Any bugs in other languages will be closed without further comment.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Breaking down on how to properly use the bugtracker
Once you have signed up, you'll be greeted with your personal overview screen. Here you'll see a handy list on your currently reported issues and their status and you can also click on the "Report an issue" button from here. Let's quickly look at each of the text fields that should be filled out and are a requirement when reporting a bug:
• Category (Requirement):
You can narrow down what type of bug it is you want to report here. There is a broad selection from everything between Graphical and Text issues to Crashes and more.
• Reproducability (Requirement):
You should always try to reproduce any bug you find, to validate it and can enter how often it happened for you in this drop-down list.
• Severity:
With this selection you can choose anything between a feature request, a text, minor or major issue or even a crash. This gives us an idea on how "bad" the reported bug is and we can better filter and prioritize bugs according to this. The default selection for this choice will be set to "minor".
• Select Profile:
Here you'll have the option of selecting one of our pre-defined profiles of the system you are currently playing on or you can enter your own. The default value will be set to "Microsoft Windows 10 (64bit)".
• Summary (Requirement):
Enter a quick and precise summary on what the bug is basically about in here please.
• Description (Requirement):
This will be the main chunk of your report - enter all information as necessary regarding your reported issue in here please.
• Steps To Reproduce (Requirement):
Please enter all the steps necessary to fully reproduce your issue in the quickest possible way in here. You can either use enumeration or a simple list of steps to present all repro-steps, such as:
1. ..
2. ..
*or*
- ...
- ...
• Additional Information:
This field might be used for any additional information which might not fit any of the others regarding your reported issue.
• Singleplayer / Multiplayer (Requirement):
Please always enter if the issue reported happened in Singleplayer or in Multiplayer as either a Host or Client.
• Asset (Requirement):
When reporting bugs, always add the asset your issue has been happening with in here. If the issue does not revolve around a specific one, simply choose "None".
• GPU Vendor & GPU Type:
You can use these fields to enter any information regarding your GPU if you think that your bug might only happen with a certain GPU type.
• Upload Files:
Once everything is filled out properly, you may add additional files such as images (.jpg), compressed videos (.mp4), log files (.txt) or XML files to the bug report to further outline the issue.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Explained: The different status changes
Once all is taken care of and your bug is ready to go, you can click on "SUBMIT" and the bug will be logged into our database. Our QA will filter through these bugs on a weekday basis and will assign or close them accordingly. The following status changes might happen shortly after your report:
"New" -> "Closed":
The bug report is invalid, wasn't properly made or is a duplicate which is already taken care of elsewhere.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"New" -> "Feedback":
The given information is not sufficient enough and we need you to add some more before we can assign the bug properly
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"New" -> "Assigned":
This means, the bug is assigned to a developer and is actively being worked on currently.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Assigned" -> "Resolved":
This means that the bug has been taken care of in two ways: Either "fixed" or "not fixable" whereas the last one means that this fix either can't be introduced to the game without causing more potential issues or we simply can't deploy the resources to fix it for the time being.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Resolved" -> "Closed":
After some time we might start closing already resolved bugs to keep the bugtracker clean - this will automatically hide them in the default view to reduce any clutter.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And that's all!
We're eager to see your reports come in and can hopefully better work through the discovered issues together in a more organized manner this way.
Best regards,
The QA Team
today we're going to be showing off our new public bugtracker starting with the following projects:
FS22 Basegame
all released DLCs so far
This is something we've been working on getting out there and want to finally start utilizing with gathering your bugs regarding our product(s).
What is this new "Public Bugtracker"?
It's a bug-tracking database we came up with for you, the players. Playing the latest DLC and found a bug you want to report? You can now finally do that in an orderly fashion directly after signing up:
https://feedback.giants-software.com/
We wanted to get away from the forum where these bugs would often get lost in the fray and won't find their way to the according developer (team). With our new bugtracker we can better handle the way you can report any findings you might discover while playing. The bugs can then be assigned properly to the according dev, similar to how our internal QA does. We can also let you know once a bug has been assigned or closed this way with just a few clicks.
What we hope to achieve is a clean environment in which bugs can be reported by anyone, filtered by our QA and taken care of or closed accordingly with a great overview of the whole process.
IMPORTANT: All bugs should be reported in ENGLISH language since that's what most of us devs communicate in here @GIANTS. Any bugs in other languages will be closed without further comment.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Breaking down on how to properly use the bugtracker
Once you have signed up, you'll be greeted with your personal overview screen. Here you'll see a handy list on your currently reported issues and their status and you can also click on the "Report an issue" button from here. Let's quickly look at each of the text fields that should be filled out and are a requirement when reporting a bug:
• Category (Requirement):
You can narrow down what type of bug it is you want to report here. There is a broad selection from everything between Graphical and Text issues to Crashes and more.
• Reproducability (Requirement):
You should always try to reproduce any bug you find, to validate it and can enter how often it happened for you in this drop-down list.
• Severity:
With this selection you can choose anything between a feature request, a text, minor or major issue or even a crash. This gives us an idea on how "bad" the reported bug is and we can better filter and prioritize bugs according to this. The default selection for this choice will be set to "minor".
• Select Profile:
Here you'll have the option of selecting one of our pre-defined profiles of the system you are currently playing on or you can enter your own. The default value will be set to "Microsoft Windows 10 (64bit)".
• Summary (Requirement):
Enter a quick and precise summary on what the bug is basically about in here please.
• Description (Requirement):
This will be the main chunk of your report - enter all information as necessary regarding your reported issue in here please.
• Steps To Reproduce (Requirement):
Please enter all the steps necessary to fully reproduce your issue in the quickest possible way in here. You can either use enumeration or a simple list of steps to present all repro-steps, such as:
1. ..
2. ..
*or*
- ...
- ...
• Additional Information:
This field might be used for any additional information which might not fit any of the others regarding your reported issue.
• Singleplayer / Multiplayer (Requirement):
Please always enter if the issue reported happened in Singleplayer or in Multiplayer as either a Host or Client.
• Asset (Requirement):
When reporting bugs, always add the asset your issue has been happening with in here. If the issue does not revolve around a specific one, simply choose "None".
• GPU Vendor & GPU Type:
You can use these fields to enter any information regarding your GPU if you think that your bug might only happen with a certain GPU type.
• Upload Files:
Once everything is filled out properly, you may add additional files such as images (.jpg), compressed videos (.mp4), log files (.txt) or XML files to the bug report to further outline the issue.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Explained: The different status changes
Once all is taken care of and your bug is ready to go, you can click on "SUBMIT" and the bug will be logged into our database. Our QA will filter through these bugs on a weekday basis and will assign or close them accordingly. The following status changes might happen shortly after your report:
"New" -> "Closed":
The bug report is invalid, wasn't properly made or is a duplicate which is already taken care of elsewhere.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"New" -> "Feedback":
The given information is not sufficient enough and we need you to add some more before we can assign the bug properly
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"New" -> "Assigned":
This means, the bug is assigned to a developer and is actively being worked on currently.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Assigned" -> "Resolved":
This means that the bug has been taken care of in two ways: Either "fixed" or "not fixable" whereas the last one means that this fix either can't be introduced to the game without causing more potential issues or we simply can't deploy the resources to fix it for the time being.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
"Resolved" -> "Closed":
After some time we might start closing already resolved bugs to keep the bugtracker clean - this will automatically hide them in the default view to reduce any clutter.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And that's all!
We're eager to see your reports come in and can hopefully better work through the discovered issues together in a more organized manner this way.
Best regards,
The QA Team