PHPAudit Loginshare Bug - No help?

[atDev]

I have a ticket open for this yet the support rep. that is handling the ticket seems to think there is not a bug, even though I gave clear instructions to duplicate the issue and I can duplicate it over and over again.

I then went on to reference about 6 forum posts where users have similar issues with multiple different loginshare modules.

I have not heard back on the ticket for a day or so. Once again im disappointed by the support. As I reported this issue months ago in a ticket and on the forums.

Loginshare issues, fixed other but not phpaudit

[craigbrass]

Please post your ticket ID and I will get Jamie to chase it up.

[atDev]

This should be it:
DUH-551114

I can not view the ticket because I submitted a seperate ticket issue months ago (when I had support paid for). Since it took so long (and still have received) to get a resolution my support has since expired so I had to have them open a new ticket for me which they agreed to do since I submitted the issue before my expiration.

[Mahesh Slaria]

Hi,

I created a duplicate issue on my Development box.

Right now, I am testing all the conditions for login share. I will update you ASAP.

Thanks.

Regards,

[atDev]

Originally Posted by Mahesh Slaria

Hi,

I created a duplicate issue on my Development box.

Right now, I am testing all the conditions for login share. I will update you ASAP.

Thanks.

Regards,

Any update?

[atDev]

Originally Posted by Mahesh Slaria

Hi,

I created a duplicate issue on my Development box.

Right now, I am testing all the conditions for login share. I will update you ASAP.

Thanks.

Regards,

?

[Jamie Edwards]

Hi atDev,

I pinged Mahesh to this thread.

[atDev]

Originally Posted by Jamie Edwards

Hi atDev,

I pinged Mahesh to this thread.

Still nothing...

[atDev]

Originally Posted by atDev

Still nothing...

I guess I got warned for this message. Just so you know I do have a ticket open for this and the only reason Im using the forum is because support does not have good communication in the helpdesk and cannot even answer my ticket for over 9 days.

[Jamie Edwards]

Your issue is being handled by a developer - the support team cannot fix bugs, therefore the ticket is not being handled by the support team. Because (unlike the support team) the developer is busy developing rather than managing the help desk, updates to tickets are not as frequent as that they otherwise are.

You have received multiple confirmations that your issue has been received and is being worked on, all we ask now is that you wait while the issue is resolved.

Thanks,

[atDev]

Originally Posted by Jamie Edwards

Your issue is being handled by a developer - the support team cannot fix bugs, therefore the ticket is not being handled by the support team. Because (unlike the support team) the developer is busy developing rather than managing the help desk, updates to tickets are not as frequent as that they otherwise are.

You have received multiple confirmations that your issue has been received and is being worked on, all we ask now is that you wait while the issue is resolved.

Thanks,

A simple question, how long do you expect a user to wait for a bug fix to be supplied? 9 days? A month? 6 months?

[craigbrass]

I'd say 1 month would be a good time frame for a bug fix based on personal experience with several companies.....

[atDev]

Originally Posted by craigbrass

I'd say 1 month would be a good time frame for a bug fix based on personal experience with several companies.....

Wow, we usually provide bug fixes to our clients within 48 hours.

[craigbrass]

I think you misunderstood me. I was first meaning 1 month maximum. Next, the developers fix many bugs in a new build. Are you expecting them to release a new release for EVERY SINGLE bug?

[atDev]

Originally Posted by craigbrass

I think you misunderstood me. I was first meaning 1 month maximum. Next, the developers fix many bugs in a new build. Are you expecting them to release a new release for EVERY SINGLE bug?

No, I'm expecting them to fix a flaw that I reported 6 months ago in the program that renders it unusable in terms of staff permission based ticket viewing.