User talk:BDJP007301

Image size in infobox
If you want to set the image size in an infobox, you have to use the additional parameter. Just adding the size after a pipe causes the template syntax to think its a separate parameter. – KnightMiner  t/c 13:10, 4 August 2015 (UTC)

Noticed "not even going to care about bugs anymore"
Burning out? It's a lot of work. – Sealbudsman (Aaron) T/C 19:52, 12 August 2015 (UTC)


 * No, its just that I'm not going to put any bugs I reported on my userpage anymore. Some of them were reported just because I forgot to change a stupid setting on the computer or the game. -BDJP (t 19:55, 12 August 2015 (UTC)


 * Oh, just the user page, I see. Well then, cheers!  – Sealbudsman (Aaron) SealbudsmanFace.png T/C 19:59, 12 August 2015 (UTC)

Speaking of bugs,
I have another idea I wanted to run past you. No this isn't tracker titles.

So it's been bugging me (ha ha, try not to laugh too hard) that on the wiki, some bugs are being listed on pages where the tracker says they were fixed, which is often different from what version of the game they were fixed. I know that on the whole, it's just easier to do it the way we're doing it, and also easier to check against JIRA queries. When I was doing it, I had a workflow, and I'm sure you have your own workflow that you're comfortable with.

So I'm trying to imagine a workflow where we:
 * 1) put bug fixes on the version from the tracker, like we already do,
 * 2) playtesting can be done, optionally or at wiki editors' lesure, to find the "correct" version,
 * 3) the bug can be moved to that version page, marked as "complete" with a template param or something,
 * 4) a category can keep track of what bugs are "complete" and what's not
 * 5) the bug tracker's job doesn't get any harder, with respect to checking for changes in bugs, whether they're open or closed, etc.
 * 1) the bug tracker's job doesn't get any harder, with respect to checking for changes in bugs, whether they're open or closed, etc.

Maybe in imagining this, I'm having a stumbling block because I'm not familiar with the methods you use. I assume from observing what you do, that you reopen and close bugs here on the wiki based on some JIRA query or queries that tell you what things were recently open / closed. That's only because that's now I was doing it. I'm not familiar with how you do it. Can you think it over and let me know whether you think this idea (of moving bugs to more accurate version pages) would be a benign thing to do, for the bug tracker stuff you do, and any examples of how it would change things, or make it harder, etc? I would like to do this, but I wouldn't do it if it were a burden to bug tracker people like yourself. – Sealbudsman (Aaron) T/C 20:22, 12 August 2015 (UTC)


 * Eh... I'm not really sure about that idea. Like, I'm REALLY not sure. Going to have to think it over for a while. -BDJP (t 03:32, 17 August 2015 (UTC)


 * Sure, I'd appreciate any well-thought-out feedback you might have. – Sealbudsman (Aaron) SealbudsmanFace.png T/C 19:18, 19 August 2015 (UTC)