Newer bugs that did not exist before or working fine previously

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • webcms
    Senior Member
    • Jan 2014
    • 172
    • 5.0.X

    Newer bugs that did not exist before or working fine previously

    I'm not sure what kind of development and QA teams you folks have but there are literally HUNDREDS of bugs being resolved in each release.

    For instance, I posted a JIRA issue for missing CSS while editing an Article a couple of years ago - this was working just fine before in the prior release.

    And now I see:

    VBV-15322: CSS missing on login form (this was working just fine before as well) - how could this POPULAR FEATURE have released without testing is beyond me.

    How come newer bugs are introduced (that did not exist before and were working fine previously) and released out without adequate testing?

    Please reduce the number of bugs by having a tighter QA process.

    TIA
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24288
    • 6.0.X

    #2
    You'll need to associate your forum account with your license, and then post this sort of thing in the correct forum - Licensed Customer Feedback.
    Site Feedback is for feedback on the vBulletin website itself only.
    MARK.B
    vBulletin Support
    ------------
    My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
    My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

    Comment

    widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
    Working...