3

If you haven't noticed, a chunk of bugs have been migrated to meta.stackexchange.com and older bugs that couldn't be migrated (due to restrictions in SE system) were deleted.

There has always been a duplicate behaviour going on when it comes to support for these [bugs] thus since meta.stackexchange.com seems to be main place for this and all SE sites run the same SE 2.0 engine it would be more beneficial to you all that questions tagged [bug] should be asked at meta.stackexchange.com.

Otherwise your questions will end up dying and forgotten due to lack of activity

1

Please restore them. It's not like deleting them will save any actual space, nor are they cluttering the place up.

It's going to be hard to complain to "the mother ship" that they're ignoring our bug reports if we don't have any bug reports to point them to.

  • 1
    That's the point. – phwd Nov 30 '14 at 13:41
1

Folks should feel absolutely fine to just post bug reports here. Developers routinely patrol anything tagged 'bug' on any child meta site (they have a consolidated overview to find them) and act on them.

Some bugs are temporary, some are known and will be fixed in future builds, some can't be reproduced, but all of them are seen. I'll talk to them again about leaving a comment noting that they've at least seen the report, but please stop deleting and migrating these - it doesn't help anything and just causes more confusion.

You do not have to go to Meta SE if you don't want to go there, it's completely optional. Any bug or support request will be handled here in turn, or migrated there by us if it really is something that's network impacting.

  • 1
    +1 - wanted to add that migrating bugs that are specific to Web Applications to meta.stackexchange is counter productive. It confuses matters and is entirely unhelpful. As Tim noted, migrating them at all is not necessary either - we see them, wherever they are posted. Moving them around, again, just confuses matters and can make contacting the OP more difficult. Don't do it. – Oded Dec 10 '14 at 7:52
  • 1
    I've already been told in the past by some SE staff to migrate some bugs that are specific to do with the network engine, so the whole don't migrate is absolutely vague. -1 to all of this. The fact that it took nearly two weeks to reply is quite something. Whatever yes. – phwd Dec 10 '14 at 10:51
  • 2
    How does it take over several months for one to realise they should probably comment on a bug or place a status on it that it's noted? How can as I mod know that you did in fact note a bug in your consolidated review and didn't overlook it? Not impressed by this response given the time delay on answers and acting on bugs in general. This isn't confusing because in the reference of this meta no one other than you knows that bugs are being seen. This isn't a week issue, this isn't even months. This has been something that has happened over years. – phwd Dec 10 '14 at 11:00
  • 2
    You do not have a clear procedure for bugs status notification on child metas. It's an empty support channel. Either it's quite known or one of us mods have to stick out heads in Teacher's Lounge and prod you ever few weeks. At the very least when the bug is migrated the user is given the option of community member support from other SE sites. So we can at least pretend like something is being done about it. – phwd Dec 10 '14 at 11:04
  • 1
    If developers routinely patrol child metas it certainly feels like the rounds are limited to Stack Overflow – Eight Days of Malaise Dec 19 '14 at 4:11
  • @pnuts - why are you assuming they are being ignored? – Oded Sep 10 '17 at 16:09
  • @pnuts - I see. So, you equate no tag to it being ignored. – Oded Sep 10 '17 at 17:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .