Can we reply to older threads in the Bug Reports subforum?

[SeekTruthFromFx]

I can't reply to some threads in the Bug Reports subforum, even ones that are not marked as locked. For example, I can't reply to this post in the Bug Reports subforum, which is annoying because it's tagged "Needs Info" and I have a savegame that reproduces the bug.

Could someone please try to reply to it? It might be a problem my end or it could be somehow bugged/shadowlocked.

 

[CaesarVincens]

Make a new report and include a link to the previous report.

 

[SeekTruthFromFx]

Make a new report and include a link to the previous report.

Were you able to post to it? I will file a bug report about the bug reports if other people can't access it either.

 

[CaesarVincens]

I hadn't tried, but given it's from version 1.1, probably best to post a new report for the latest version anyway.

 

[prismaticmarcus]

Yeah, since it's not your bug report it's best to make a new one.

 

[SeekTruthFromFx]

I am very surprised by this advice from @CaesarVincens and @prismaticmarcus . Normal bug reporting practice is that a new bug report describing the same problem as an old bug report is marked as a Duplicate (and the Forum has a Duplicate tag for this purpose, which QA do use). It is then ignored, so that all information about the bug is on a single page and to avoid the disaster of two devs trying to fix the same bug (which is a a waste of resources and has the potential to introduce conflicts).

I know that PDX has a separate, internal bug reporting system (Jira). But we don't know whether the original bug was ever entered into Jira, because it's currently tagged here as Needs Info.

So what I expect to happen if I open a new bug report:
- QA see my bug report, find the original bug report and mark mine as Duplicate, so it's not transferred to the internal bug report database.
- the original bug report remains tagged as Needs Info, so is ignored by the manager allocating bugs to devs
- so the bug is never allocated to a dev to fix.

What am I missing here, please?

It's no trouble to file a new bug report, I have the text already written, but at the moment it feels doomed.

 

[prismaticmarcus]

This is from the Forum Code of Conduct (I've coloured the answer to your question, @SeekTruthFromFx)

Bumping and necroposting​

Making short posts made with the sole intention of keeping a topic near the top of the board is called “bumping”. This clutters unnecessarily the forums and means that other active threads are moved down the page. As such, bumping is not allowed, and posts in this vein will be removed.

Where possible, please avoid posting in threads that are reasonably old (6+ months) as they are likely to be outdated and/or irrelevant, especially when reporting a bug.

The QA asked for more info from the OP, not from anyone who happens to have a similar looking issue which may in fact be quite different.

 

[SeekTruthFromFx]

This is from the Forum Code of Conduct (I've coloured the answer to your question, @SeekTruthFromFx)

Bumping and necroposting​

Making short posts made with the sole intention of keeping a topic near the top of the board is called “bumping”. This clutters unnecessarily the forums and means that other active threads are moved down the page. As such, bumping is not allowed, and posts in this vein will be removed.

Where possible, please avoid posting in threads that are reasonably old (6+ months) as they are likely to be outdated and/or irrelevant, especially when reporting a bug.

The QA asked for more info from the OP, not from anyone who happens to have a similar looking issue which may in fact be quite different.

Thank you for taking the time to repeat part of the CoC here. If that's what PDX want, then it's no trouble to do that.

I filed a fresh report yesterday and it will be interesting to see what happens to it. QA are actively processing reports, which is always encouraging.