I lack of communication in the bug reporting process

[worried]

Personally, I feel the bug tracker process is interfering with communication. It's something developers are familiar with--The opposite is true for customers so we are at a loss navigating it. In one reported bug, I commented that I found the cause of the problem. The developer then misinterpreted my comment as the issue being resolved which is not the case.

There needs to be plain dialog as well so our complaints aren't lost in the bug tracker. Also, assume we don't know bug tracker jargon. There's a real lack of communication going on here.

[IBxAnders]

What is the issue # ?

[worried]

http://tracker.vbulletin.com/browse/VBM-1370

Maybe I misunderstood his response.

[Ramsesx]

http://tracker.vbulletin.com/browse/VBM-1370

Maybe I misunderstood his response.

I understand it like you did, maybe he had a bad day.
Curious:
Status: Resolved
Resolution: Won't Fix

[Stefano Acerbetti]

sorry for the misunderstanding ...

I got confused, and reopening the bug

[acwatts]

When I first looked at the Jira thing I thought it might as well be in Chinese. Don't know how you navigate to see all mobile suite issues, It is the most confusing thing I have ever seen on the internet.

[Mark.B]

Jira is certainly confusing for the "public" to use, I stay out of it unless i absolutely have to.

I think there are actually two issues that put people off:

1) It's too confusing
2) There is a perception that using it is a bit of a waste of time.

There has to be a better way but i don't profess to know what it is.

[Loco.M]

just my 2 cents,, I read this

Found reason for problem.

as "I found out what I did and it's fixed" since it was posted later that day..

[silkroad]

Agreed!

Jira was specifically designed for use by software development teams, not customer service and customer support. Yes, Jira would like their tracker to be used for customer support; and yet vBulletin would like all their customers to be ad hoc members of their software development team; and yes, Jira is no substitution for good customer service; which has 'flown out the window' every since the canned reply to vB Bugs is now "submit your bug to Jira".......

vB should not force paying customers to submit vB bugs to Jira. They should return to customer support and have their software development team use Jira, and publicly insure that Jira is optional for customer submissions and return to real customer support; however, this is unlikely, since anyone who disagrees with vB staff is subject to anti-customer slogans, phrases and harassment.

[CK]

How about this one, marked as resolved, can't petition to reopen.

http://tracker.vbulletin.com/browse/VBM-1079

[Trevor Hannant]

If it's as designed then you need to make an improvement request to have the functionality changed. If it's not working as designed, it's a bug

[m0rgulvale]

please pay me for my time if you want me to be reporting bugs. when you release software, try to make sure the obvious bugs are not there (e.g. registration working with captcha enabled). customers shouldn't have to be involved hunting down bugs. if you can't hire your own team to do quality assurance testing, at least pay customers for their help reporting bugs. this is a waste of my time and money.

[Uberguilds]

Spend $300+ just to sit in the bug tracker all day~

wooooooooooooooooooooooo


Hoping an update is somewhere around the corner. Page navigation is absolutely atrocious if you have a 3,000 page thread. Click into the showthread, start at page 1, scroll horizontally for 40 seconds before you get to the last page. There are numerous issues that were obviously not even thought about or a result of lacking talent.

Goto unread post in a thread; is this not an important aspect of forums in the eyes of vBulletin? Will it cost an extra $50?


Users are highly disappointed in this project, not just the community leaders. We are gasping for air on an update bros.

[CK]

If it's as designed then you need to make an improvement request to have the functionality changed. If it's not working as designed, it's a bug

I'm going to log a sarcastic bug now