Quote Originally Posted by dark494 View Post
Actually posts are automatically moved to the accepted bugs forum as long as they have the proper template. I've made numerous bug reports that have gone completely ignored, or were merely patched/fixed at a random time without announcement and that bug report has sat and collected dust in the accepted bugs forum ever since.
You clearly don't work in software development. There really is no reason for them to tell us what bugs they are or aren't fixing, or their timetables for such. Even if a fix is in the works, it might be internally complex to fix and not worth the time compared to higher-priority issues.

If SE works anything at all like my company, they likely have some supervisor, specialist, or development representative glance at the bugs reported on the forum that passed the initial "is this reported correctly" check (which is probably done by a forum moderator). The person looking at the issue might know the code in question at all, and even if they are a programmer/developer, the bug isn't necessarily in the area of the code they work with. The reviewer might have a reaction like, "Yup, that's definitely a bug," or "Nope, definitely working as designed," but there are other possible reactions too. "Sounds like a bug but I don't have the time to reproduce it right now to verify it's not just the submitter's computer going crazy," "I think that might be a bug, but I'm not sure and would have to ask around to see if it's actually a bug or not," or "Huh, that's weird. Someone will have to follow those steps later and see what happens!" When someone has to look at the code in any sort of depth, we would consider the bug "accepted." That doesn't mean it's accepted that the issue is definitely a bug and will be fixed. It means it might be, and someone has to look at it to make sure. It could turn out to actually work they way they intended it to, or to be a low-priority cosmetic issue that no one has the time to look into without taking time away from content updates. "Accepted" bugs likely go onto a list somewhere, possibly with a priority for how urgent it is that a development programmer examine it, and when someone has the time, they look at a few bugs on that list.

Software development isn't magic. Developers only have a finite amount of time. No one is going to work twelve-hour days to resolve some cosmetic bug in their software (okay, some coders will, but they're crazy!). Please don't be hostile to coders just because an issue you reported wasn't prioritized above everything else in their lives, or that they didn't track the bug back down the chain of contact (which might go something like moderator->reviewer->supervisor->specialist->developer->coder) to figure out who reported it to tell them personally about the resolution.