bugs aren't being reviewed

[Mazinger]

I report some bugs in the bug tracer, some of them get marked as Cannot Reproduce & Not a Bug.

Then I post another reply to make it clear, and bring screenshots... etc

I find no more replies nor marking from the developer - unless I bump the report many times - because it's already been marked...

My suggestion/questions is: Is there any way to ensure checking reports that has already been marked?

[Wayne Luke]

Not really. If a reply is made it is moved to the top that is about it.

However just because you might have a problem with something on your site, doesn't make it a bug.

My suggestion is to make your reports as clear as possible and include the screenshots when it is first submitted.

[Mazinger]

It's not a problem in my site. Just a bug in vBulletin itself.

I know the bug get moved to the top. However, I see developers neglect it since they see it already marked.

[Marco van Herwaarden]

Developers will monitor all bug reports. They however will not always repsond to them or not respond each day.

[Mazinger]

Some bugs which are marked as Awaiting Feedback has taken more than a month. Example: http://www.vbulletin.com/forum/proje...?issueid=21741

The real problem is with bugs marked as Fixed & Not a Bug - after they get marked, developers don't give attention to following replies.

[Wayne Luke]

I can't recreate the bug you listed in the lastest version, 3.6.4 or 3.6.5.

[Mazinger]

I've replied.

[Mark.B]

I've found that often it can take a week or so for any follow up from developers, so it's just a matter of patience really.

[Colin F]

Issues that say 'Awaiting Feedback' will always be looked at again.

If you don't agree with the status of an issue that's set to 'Fixed' or 'Not a Bug' then you can petition for it to be opened again when you reply. Be advised that the developers generally have reasons for why they set an issue to 'fixed' or 'not a bug', so you don't want to be rehashing whatever's already been said.

[JakeS]

Mazinger, did you check your bugs on a FRESH installation?

[Mazinger]

Issues that say 'Awaiting Feedback' will always be looked at again.

If you don't agree with the status of an issue that's set to 'Fixed' or 'Not a Bug' then you can petition for it to be opened again when you reply. Be advised that the developers generally have reasons for why they set an issue to 'fixed' or 'not a bug', so you don't want to be rehashing whatever's already been said.

I'm not sure about 'petition for it'... it might be a feature in the project tools, which I'm not aware of it yet.

But sometimes I report bugs with no clear describtion of the problem, and developers mark them as Not a Bug. Then I reply with clear describtion, and how to reproduce, and a provide screenshot... But I still don't get an answer unless I bump the report several times. There are many real bugs now which are marked as Not a Bug before I reply again... and they got lost in remote pages.

[JakeS]

I just tried one of your bugs (one marked as not a bug) and I cannot see the bug on a fresh install, are you sure you tested on a fresh install?

[Mazinger]

Yeah. I reproduce my bugs @ the admin demo. And ofcourse not all of my (not a bug) reports are real bugs.

[JakeS]

Yeah. I reproduce my bugs @ the admin demo. And ofcourse not all of my (not a bug) reports are real bugs.

The Admin Demo is not 100% fresh got a couple of modifications. (Templates)

Give me a link to one of your bugs you think is real and I will try it out.

[Colin F]

Mazinger, you can choose to petition to a certain status by selecting it from the dropdown box when replying.

First off, you'll probably want to provide as clear a description as possible when first reporting the bug. Also, keep in mind that what you consider to be a bug may not be the same as what the developers consider a bug.