Order of Battle Bug Database

[AMG]

Hello all,

I've set up a bug database to allow for easier and more efficient bug reporting and tracking and to offer you all a place to provide bug information and keep apprised of updates and fixes that are inbound.

If you would like to be a part of this new process and contribute to the database, please pm or email me (adamg@slitherine.co.uk) with your email address, this is needed for creating accounts.

For all other users, if you wish to continue posting bugs or feedback, please try to keep to the following format when reporting your bugs, as this will allow us to quickly and easily migrate the details from the Forum to the bug database;

Issue Type: Bug/Feedback/Change Request
Summary: Please provide a one-line simple description of the issue
Description: Please offer a concise but detailed description of the bug/feature/request, as well as steps needed to reproduce. This will allow us/the devs to quickly reproduce your issue and help expedite the fix/change.
Category: Audio, Crash, Editor, Gameplay, Visual/Graphical, PBEM, Text, Stats-related

Also, please attach any images/screenshots/videos that might help us resolve your issue.

I will periodically share a "state of play" report on the forums of the bugs opened, fixed and patch schedules.

If you have any questions, please feel free to email, pm or reply below.

Cheers,

Adam

[bru888]

This has been a long time coming. I am inspired and enthused. Reinvigorated may come next, we'll see. Time and energy are limited, as always.

But thanks; this is an important function that has been missing and holding OOB back for years. Communication, guys. Speaking for the community, it's what you need to make the game better and enhance sales.

[bru888]

Okay, I have transcribed the 15 issues listed so far in the Current Bugs 7.1.4 thread to the Bugs Database. Commentary is sparse because the discussions and screen prints are shown in the linked threads and need not be laboriously reproduced in the database.

Here are two recommendations:

Folks who have access to the database, I would not overwhelm the process by posting each and every minor issue. That's what I was trying to due with the Current Bugs thread: triage for manageability.

Adam and the developers, that said above, you still need to look through those threads for additional improvements that could be made and for updates offered by community members. For example, terminator just posted in the Current Bugs thread some clues as to what is going on with specialisation bugs. There was an update in 7.1.4 in the campaign editor to include additional dating functions and this seems to have opened up some possibilities for conflicts and typographical errors.

[GabeKnight]

I'll help if I can.

Don't understand the new account procedure, though (?)
But you can use my email I've registered with this account.

PS That was fast with the database...

[AMG]

Adam and the developers, that said above, you still need to look through those threads for additional improvements that could be made and for updates offered by community members. For example, terminator just posted in the Current Bugs thread some clues as to what is going on with specialisation bugs. There was an update in 7.1.4 in the campaign editor to include additional dating functions and this seems to have opened up some possibilities for conflicts and typographical errors.

Thanks bru888, if users who aren't reporting to the database please outline in the thread summary if the post relates to either; BUG:, CHANGE REQUEST:, or FEEDBACK: that would be really hopeful to me for filtering out these kinds of topics. Thanks!

I'll help if I can.

Don't understand the new account procedure, though (?)
But you can use my email I've registered with this account.

PS That was fast with the database...

Hi GabeKnight, you can email me (adamg@slitherine.co.uk) with an email address you would like to use for the bug database, and I'll create your account (you'll get an invite to connect to the database).

Thanks,

Adam

[GabeKnight]

Okay, now I get why a new account's needed.

Quick question, Adam: Do you want reports like the one of the Norway scen inside the database, too? I mean, it's rather minor, cosmetic stuff only. Don't get me wrong, it should be fixed eventually, but with really low priority.

[AMG]

Okay, now I get why a new account's needed.

Quick question, Adam: Do you want reports like the one of the Norway scen inside the database, too? I mean, it's rather minor, cosmetic stuff only. Don't get me wrong, it should be fixed eventually, but with really low priority.

Yes, that's fine to add. If you feel something is important or trivial, you can set the priority appropriately, I can later triage the issues before assigning the ticket to the developer.

Thanks!

[bru888]

Thanks bru888, if users who aren't reporting to the database please outline in the thread summary if the post relates to either; BUG:, CHANGE REQUEST:, or FEEDBACK: that would be really hopeful to me for filtering out these kinds of topics. Thanks!

Nice to see the activity in the database this morning. Whoever the person is whose initials are TP (I won't name names here) that you assigned all of this stuff to is going to be a very busy person!

Regarding what you wrote above, it is my impression that this is all about bugs and only about bugs. The Current Bugs thread is, of course, about bugs, and in the bug database, there is only one choice in the dropdown menu: Bug

Image0290.jpg (190.41 KiB) Viewed 7179 times

[13obo]

Change request pertains to bugs as well in the sense that you say what behaviour do you expect to see when the bug is fixed. Most times, it is clear how something should behave, but sometime, it is not- for ex. E-100 specialisation should be fixed, but what should be the new date for the specialisation?

[AMG]

Nice to see the activity in the database this morning. Whoever the person is whose initials are TP (I won't name names here) that you assigned all of this stuff to is going to be a very busy person!
Regarding what you wrote above, it is my impression that this is all about bugs and only about bugs. The Current Bugs thread is, of course, about bugs, and in the bug database, there is only one choice in the dropdown menu: Bug

feedback and change requests in here please.PNG (25.17 KiB) Viewed 7148 times

This is where the different categories can be entered.

The Tracker: Bug is a default header in redmine. Not the clearest but never mind.

[bru888]

Ah! Very good. But still, I would offer again this recommendation: "Folks who have access to the database, I would not overwhelm the process by posting each and every minor issue. That's what I was trying to due with the Current Bugs thread: triage for manageability." Meaning in this case, keep the database for bugs only, not feedback and feature requests. Let's see if this is going to work on that basis first.

[bru888]

Let's see if this is going to work on that basis first.

By the way, folks, it does seem to be working. I see more activity this morning; responses and updates.

[GabeKnight]

@Adam

Again, one (more or less) simple question: How do you want the unit's issues handled within the database? Just one "bug" ticket linking to the Unit Issues 7.1.4 thread or as separate topics?
If you want to create a separate ticket for every unit issue (terminator and Admiral found like 30 issues alone), you better assign someone to do it, because I know I won't transcribe everything into that database myself...

On the other hand creating separate tickets seems to be the only feasible way to make sure that each and every unit-issue has been tracked and fixed.
On man, I hope you have a better idea for a good solution...

[bru888]

Heh, I don't know about you, Gabe, but I am not volunteering to separately transcribe every issue in a compilation thread like Unit Issues 7.1.4. I created that thread to hopefully concentrate such issues whereas before they would be mentioned in passing in threads like Andy's "Mistakes vere made, mein Fuhrer" (a misleading thread title because some folks believe it was intended for buggy "mistakes"). Developers can look through such a compilation thread at their leisure, once they have been directed to it, and glean from it what they will; it may be advantageous to do so because they see more discussion and detail that way. In any case, it's above my pay scale to be entering each of those issues in the bug database individually.

[AMG]

@Adam

Again, one (more or less) simple question: How do you want the unit's issues handled within the database? Just one "bug" ticket linking to the Unit Issues 7.1.4 thread or as separate topics?
If you want to create a separate ticket for every unit issue (terminator and Admiral found like 30 issues alone), you better assign someone to do it, because I know I won't transcribe everything into that database myself...

On the other hand creating separate tickets seems to be the only feasible way to make sure that each and every unit-issue has been tracked and fixed.
On man, I hope you have a better idea for a good solution...

One ring to rule them all! As this isn't a formal testing process, its fine combine them into one issue. I can always split them out based on the fixing process.

Heh, I don't know about you, Gabe, but I am not volunteering to separately transcribe every issue in a compilation thread like Unit Issues 7.1.4. I created that thread to hopefully concentrate such issues whereas before they would be mentioned in passing in threads like Andy's "Mistakes vere made, mein Fuhrer" (a misleading thread title because some folks believe it was intended for buggy "mistakes"). Developers can look through such a compilation thread at their leisure, once they have been directed to it, and glean from it what they will; it may be advantageous to do so because they see more discussion and detail that way. In any case, it's above my pay scale to be entering each of those issues in the bug database individually.

As this database is new, there will always be more reporting activity to get it populated. I'm guessing once it's populated (or at least covering the majority of serious issues), the process of adding new items will be significantly faster and less often. With that said, I really appreciate the help you've all put in so far!

[bru888]

Thanks for your help in this, Adam. My thinking was to segregate and highlight the serious issues while compiling others of a less important nature. That is not to denigrate those other issues - we do want to have the best OOB with the best units possible - but aside from our own time and effort, we don't want to overwhelm the developers with dozens of issues in the database.

[AMG]

Sounds like a plan to me, cheers!

[bru888]

I noticed, by the way, that it's important to keep the database sorted by "Updated" so that one can see if there is any recent follow-up activity. For example, I just asked a question about Battle of Britain and saw that the issue popped to the top of the list even though it is marked as "Resolved."

[AMG]

I noticed, by the way, that it's important to keep the database sorted by "Updated" so that one can see if there is any recent follow-up activity. For example, I just asked a question about Battle of Britain and saw that the issue popped to the top of the list even though it is marked as "Resolved."

The order of issues and their current state is on the user side. I cannot set the order filter for all users, unfortunately. You can, however, set your own filters to see Updated tickets first.

[GabeKnight]

Progress! Progress! Progress!

I think this whole BugDB thingy is on the right track. Many issues being reported and worked on with a new patch in the making. Thank you!