Announcement

Collapse
No announcement yet.

Notification system overhaul.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • rmwebs
    commented on 's reply
    Give it 6 months and it'll be EOL when vBulletin 6.0.0 Alpha 1 is released as a stable product with a $200 upgrade fee.

  • IcEWoLF
    replied
    Obviously this is not going to be implemented and nothing is being done according to JIRA. They are obviously not seeing how much of a flaw there is that there is no true notification system in vBulletin...makes me question the way management and developers think about vB5...

    Let this sink in, its been almost 2 years since this was released and we still don't have an acceptable product here.

    Leave a comment:


  • Kent55
    commented on 's reply
    I totally agree.

  • Mark.B
    replied
    Originally posted by Kent55 View Post
    What I don't get is why the vBulletin development process needs to be so strict that customers struggle to get their voices heard. Other software like XenForo and Woltlab Burning Board are so much better at hearing customer's suggestions. I requested two features over at Woltlab and both were implemented. The reason that it is so smooth is that the developers are on the forums reading suggestions and talking to customers. The fact the vB developers don't even read these sorts of threads is exactly why customer's feel that they are ignored, because the Support team have no influence on what gets implemented and there is no way of getting a new feature without using the wonderful JIRA, which is filled with an obscene amount of bug reports.
    Even if it could be done via the forums, it would still be best practice to include demo screenshots from the actual product, not a re-imagined version.

    Leave a comment:


  • Kent55
    replied
    What I don't get is why the vBulletin development process needs to be so strict that customers struggle to get their voices heard. Other software like XenForo and Woltlab Burning Board are so much better at hearing customer's suggestions. I requested two features over at Woltlab and both were implemented. The reason that it is so smooth is that the developers are on the forums reading suggestions and talking to customers. The fact the vB developers don't even read these sorts of threads is exactly why customer's feel that they are ignored, because the Support team have no influence on what gets implemented and there is no way of getting a new feature without using the wonderful JIRA, which is filled with an obscene amount of bug reports.

    Leave a comment:


  • Mark.B
    replied
    What I've tried to do in this thread, is provide advice for how best to get the requested changes implemented, within the confines of the system that is in use. That system isn't going to change, so the best advice is to work with it. Far from being 'screw you', my posts will help people to have the greatest chance of having their suggestions implemented.

    Leave a comment:


  • rmwebs
    replied
    Originally posted by Mark.B View Post
    Could you please point to where any of us has said that?
    Re-read the entire thread with a fresh pair of eyes Mark. The attitude from yourself and other staff members comes across as very much "screw you, we know what we're talking about". The problem is either most of you have an amazing amount of patience with the developers, or you're extremely bias and cant see how flawed vB is right now, both as software and as a company.

    Leave a comment:


  • Mark.B
    replied
    Originally posted by Miykichii View Post
    Terrible management, they look at us and say "they have no idea what they are talking about"
    Could you please point to where any of us has said that?

    Leave a comment:


  • Mark.B
    replied
    Originally posted by IcEWoLF View Post
    To me this thread is the perfect example of vBulletin driving people away...whats the point of feedback if you are being stubborn? Devs can simply look past all the designs and get the idea of we really need to make a better notification system because the current system is so 1999.
    I don't even know why we bother trying to help anymore either.
    They aren't going to "look past the designs" - the development team follow clear, defined processes. If you, me, or anyone else want to influence change, then the best way to do that is to follow those processes and use the current, default product as a starting point.

    If people wish to instead include screenshots from what amounts to a completely different and fictitious product, then this is going to greatly hamper the chances of the actual request being implemented. That's a simple fact, and nothing any of the support team can do will change that.

    All I'm trying to do is provide accurate advice on the best way to get the requested changes into the product based on the current developmental practices. I can't change those developmental practices, so if my helpful and informed advice is ignored, you know what I'm going to say if anyone complains that the requested changes were never implemented.

    In short: don't shoot the messenger. There are processes that we need to work within.

    Leave a comment:


  • Miykichii
    replied
    Terrible management, they look at us and say "they have no idea what they are talking about" we look at them and say "you aren't listening and assessing the situation more carefully" - just leave it to time, i am enjoying vb 4.x until the slow turtle moves from vb 5.x to vb 6.x may be. But i hope as a company in the business field, they don't regret these moves.
    Last edited by Miykichii; Wed 16th Jul '14, 8:18pm.

    Leave a comment:


  • IcEWoLF
    replied
    To me this thread is the perfect example of vBulletin driving people away...whats the point of feedback if you are being stubborn? Devs can simply look past all the designs and get the idea of we really need to make a better notification system because the current system is so 1999.
    I don't even know why we bother trying to help anymore either.

    Leave a comment:


  • Miykichii
    replied
    Then we go back to square 1 again, terrible management leads to this. At the very least, Vbulletin support team should relay to the developers, customers' concern, then the devs if they find this too much work for them, either priorities the requested features or ask from the higher ups to look at hiring more developers for assistance. This is how proper successful business works.

    That is why i see VB 5.x will take 2 - 3 years to reach a more stable, proper level at this pace of development.

    Leave a comment:


  • IcEWoLF
    replied
    It's painful to even visit these boards on a mobile up, without a proper notification system vbulletin has no future. This place has become deserted if you look closely.

    Leave a comment:


  • Miykichii
    replied
    Mark - we went this long rout just to hear this "The place to push for implementation, is within the JIRA itself. The developers will not read threads such as this." this is funny.

    Vbulletin is like Xbox 1 vs PS4, when Xbox 1 came and said "gamers who bought used games, will have to pay a fee to Microsoft to play used games" everyone was angry and that angry showed through canceling the per-orders and when PS4 said "we would never do such thing" we saw many pre-orders and now Microsoft found itself in a terrible situation.

    Same thing for Vbulletin, it won't be able to gain many customers to buy or upgrade to VB 5.x unless they change their game and do what customers wants to see, if they don't get it, time and sales proves it better for them.
    Last edited by Miykichii; Wed 16th Jul '14, 4:53am.

    Leave a comment:


  • Mark.B
    replied
    The screenshots are better, certainly.

    Personally, I would have done them from the forum home because what you're showing there is still a non-standard vBulletin page. By doing this, you are adding confusion and reducing the chances of the JIRA being looked at. The devs need to see your proposed change in a *completely default page*, not a page that just happens to contain your other ideas.

    I can see what you're trying to do...you're thinking that by including your other changes in the screenshots, the devs will say "oh, that looks good, let's implement that as well". This is flawed thinking, the development process simply doesn't work that way.

    Unless you include a screenshot of a completely default page, this is going to struggle to get anywhere.

    Additionally - for the avoidance of doubt, I cannot personally get this implemented, and bumping this thread will make no difference to that. The place to push for implementation, is within the JIRA itself. The developers will not read threads such as this.

    Leave a comment:

Related Topics

Collapse

Working...
X