-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Showing developer posts only. Show all posts in this thread.
- Status
You mean "we'll never add money to HoI without a system of dynamic floating exchange rates, currency arbitrage, HoI4-themed traveller's cheques and international traders that rig currency interactions to make extra-large bonuses", aye?
The only floating exchange I accept is the exchange of 18.1 inch shells from several dozen miles away.
I'd like to put in a suggestion for a naval dockyard management simulation mini-game
I'd play it
- 27
- 3
- 2
- 1
- 1
We cannot expose the database that we use since you need to authenticate against it, contains information about future content and personal information if that's what you are asking
- 14
ok let me show you.
This is how jira looks like
This is how mantis looks like
and this is Azure
Obviously none of these examples are any from out database, but public example images (I scrubbed names just to be safe and courteous), but these are common systems for handling bugs and they all look somewhat the same, at least in general structure.
As you can see all have a reporter tag attached to them. exporting them would like whatever name and assignee to those jiras (say in a text file with said datastructure). Scrubbing away that data would be, well, I wouldn't wanna do that.
Current state would also be attached to this data, same as repro steps and files, which also can contain meta information about a user. Maybe I wrote "I did this with X tester name" and now it is in the description, you have access to it and bam, now you have some personal info.
Maybe someone has their real name as username, it gets saved in a file, someone opens it and bam, more personal info exposed. Now imagine this as a datastructure, and the data is all intermingled like so, just trying untangle that from the "bug" information would be a nightmare if even possible.
And if something goes wrong at that export it could lead to all sorts of things being leaked
Just to imagine the sheer size of our database, the amount of issues is a lot bigger than the public bug forum here. That is not a brag mind you, it is simply to give you a perspective of the amount of data being processed by any company.
If on top of this developers can resolve and QA can create a lot of issues in one day, like a lot lot.
Even if I hypotethically managed to export everything, scrub everything, absolutely nuke everything. How would I show it to you? Its just a big exported file that is supposed to run on a server via a webbrowser, its not like I can just link it in google drive and you can scrub through it.
Now I am saying this just to give a perspective on how this all work, not to just be a "debbie downer", but to explain the sheer logistical improbabilities that would have to be overcome. Its not just "one" problem, its every problem.
Thats on top of people that would have to be convinced internally.
Im not saying it is an impossible thing, but an improbable one. There is probably a smart way of handling it, but I don't have those answers now, and I just wanted to explain why it would not be an easy thing, like just flipping a switch
I hope that is at least a bit informative if nothing else
Last edited:
- 34
- 9
- 1
- 1
- 1
Afaik there is no support for that on the forum side for that atm and no integration into the database for it.
The forum team is a separate entity entirely outside the scope of PDS, and while I personally don't think it's a bad idea within reason, it's not something that I can champion myself at this stage as I have other internal stuff that I want to champion and deal with first.
I think you are underestimating the work required to make such a thing work and the amount of people needed to get involved from various stakeholders
- 9
- 2
I was more considering a more automated system that mirrored the internal status of the database and presented it as is,
There is no organizational challenges about going through issues manually and copy pasting them into the database if thats what you were refering to, more like a matter of priority. In fact the last time someone did scrub through a part of the forum was today, but they probably missed flipping the sign; or rather I miscommunicated the task, which is something that we and I can get better at.
However I will never force anyone to write in the forum though, thats on their own perorgative as most developers do not want to have a public facing persona. Yes, that includes writing in the bug forum. Flipping a sign is ok tho, ill look into it.
Hopefully our cadence will increase but it requires that the QA team stands on a stable ground with good processes. The studio split that happened last year allows us more leeway into improvement in these areas, and I admit that in regards to player communication about bug fixes we have not been as communicative as players expect us to. It is not unimportant, I just need to find a time to deal with it in a sane manner, a lot of small tasks that QA does besides bug hunting often stack up
As for reporting issues internally we usually check if its actually a bug before transfering it to the internal database, so we are not stricly copy pasting issues into the database, but are actually regressing them. In a recent cleanup of bugs 33/164 issues were reportable, others were already fixed, wad or otherwise unable to be reported. So approx 20% were actually issues. So when we do these regressions it is not only going through a couple of issues and copypasting them, its verifying that they are actually issues.
So there are no issues doing it, but it takes time to verify them, so it becomes a matter of priority and where we are in the project.
- 13
- 2
- Status