Where is the bug tracker?



  • Like bugzilla for mozilla.. where is the vivaldi equivalent tracking website?



  • @koolio The bug tracker is closed. Some insiders have access to it.

    Submit a Bug Report




  • If you found a bug, please report the issue to the developers to fix it.

    How to do a bugreport for Vivaldi
    Report each bug seperately at https://vivaldi.com/bugreport/
    Describe the issue as precise as you can.
    Add some information about extensions you use.
    Add information about the operating system and version you use.
    If you have problems with video or audio give us information about your installed codecs and graphics card/GPU.
    Add a exact link to the page where the issue comes up and can be tested.
    After reporting the issue, you will receive a confirmation mail from the bugtracker.
    In a reply to this mail you can add more information and files (like screenshots or testcases) as attachments and it will be added automatically to bug report.
    If you have questions about the bug please ask in forum first and do not forget to post the VB-XXXXX bug number (you can find it in confirmation mail).

    Thanks in advance for helping us to make Vivaldi better!




  • There isn't an open one and I've never understood why. This has been the case in the old Opera and also in Vivaldi. I can understand the need to hide security bugs, but I can't understand the reason to not show other kinds of bugs.

    If there was some Bugzilla for Vivaldi, it'd help in tracking the bugs, curtail the amount of bug duplicates due to ignorance about what bug reports have been filed, and allow users to see if bugs that interest them have been acknowledged by the devs so that they can keep an eye out for the progress of such bugs.

    Still, for whatever reason, Vivaldi has kept with the Opera secret bug reporting. I'm sure they've heard all the arguments before and haven't been swayed by them, but that doesn't stop the wondering why.



  • @Koolio No, you will not get a more public bug tracker, that was a decision made by Vivaldi dev team.

    if you are interested about a special reported bug, ask me or other mods, they could tell you what fix may be in progress.

    @Gort All your ideas are ok, but to make the tracker not-public has been discussed internally more than once.



  • Sure, I've been using Vivaldi and Opera before it for enough time to know that the decision about a public bug tracker has been made for specific reasons. That still doesn't answer the whys about such a decision. Just seems like a wrong move to me, but then I'm only human and do err.



  • @gort said in Where is the bug tracker?:

    That still doesn't answer the whys about such a decision.

    I can really say it. But i guess such things:

    • Not all content is for public.
    • Programmer-patched JIRA plugins are needed to filter the developer content into public-only content
    • More internal helpers are needed to remove the hundreds of duplicates and of unneeded requests when this-or-that pet bug will be fixed.
    • And so on…

    Trust me, it is enough work for a small team to keep the eye on current bug tracking and testing.



  • @gwen-dragon Thanks for those answers. I do get that there are drawbacks, like the ones you mention, even if I do think a public bug tracker would be beneficial. I just wish there was some official response against it, seeing that a public bug tracker has been requested over the years. Then again, maybe I missed it.

    Anyway, thanks for your time.



  • @gort said in Where is the bug tracker?:

    I just wish there was some official response against it, seeing that a public bug tracker has been requested over the years.

    I remember there was some answer from a Vivaldi official, but i do know know where.
    Please search in the forums for public bugtracker or similar words. You want to know it, you may invest some more time.



  • they should have a private and public tracker like https://issuetracker.unity3d.com/



  • @koolio said in Where is the bug tracker?:

    they should have a private and public tracker like https://issuetracker.unity3d.com/

    Actually, there is no "should". Whatever mechanism Vivaldi chooses to use in tracking software bugs is theirs alone to decide, as is the level of public access they choose to apply, if any. The browser is free, and the terms and conditions of its development are entirely up to Vivaldi. Depending on how a bug tracker is used internally, there may be all kinds of proprietary or easily misunderstood traffic derivable from the tracker besides the bug IDs or descriptions users may be aware of. How bugs are handled, grouped, or their specific progress all contain potentially proprietary information that could be mined about the nature and pace of browser development.

    Moreover, the care and feeding of user inquiries about a specific bug's progress (or lack), the meaning of developer notes about it, and so on would all represent an added overhead burden not needed for a private bug tracker. Finally, how bugs are allocated for fixing is almost certainly affected by the internal workflow of regular development (eg: fixing a bug in a particular menu would most likely be best done while redesigning or updating that same menu in normal workflow; alternatively, it might best be handled during a general repair or revision of the entire menu scheme); until internal workflow picks up a related bug, there would appear to be no progress on the bug, and that would almost certainly lead to the same user complaints as occur when there is no public access to bug tracking.



  • @koolio said in Where is the bug tracker?:

    they should have a private and public tracker

    More work to deal with double trackers.
    I guess, It may decrease the workflow. Thats my opinion.



  • @gwen-dragon said in Where is the bug tracker?:

    @gort said in Where is the bug tracker?:

    That still doesn't answer the whys about such a decision.

    I can really say it. But i guess such things:

    • Not all content is for public.
    • Programmer-patched JIRA plugins are needed to filter the developer content into public-only content
    • More internal helpers are needed to remove the hundreds of duplicates and of unneeded requests when this-or-that pet bug will be fixed.
    • And so on…

    Trust me, it is enough work for a small team to keep the eye on current bug tracking and testing.

    On the other hand, it's a good thing if users can see which bugs keep being ignored for a long time. With a private bug tracker it is easier for devs to become lazy and start to ignore bugs, giving responses like "works as intended" and so on. I mean, in the long term.



  • @rammix said in Where is the bug tracker?:

    With a private bug tracker it is easier for devs to become lazy and start to ignore bugs, giving responses like "works as intended" and so on. I mean, in the long term.

    You think the small Vivaldi team lazy and ignorant? Such poisonous post.
    My personal advice: Do not use the product if you dislike the developers and please leave the community quickly.

    The devs are not lazy and do not ignore bugs.
    Bugs are tested by internal testers first, the revised by devs, may be closed as Not Reproducible or Fixed, and if such issue reappears later bug can be reopened.



  • This week there were 3 snapshots with fixes, that's what really matters to me and people shouldn't bother to look at the bugtracker, what difference makes to anyone to look at some list of unfixed issues? Fixes are coming out, in given time. Just do your part and report.



  • I repeat a very nice idea, which someone wrote in one of the past blogposts:
    setup an autoresponder, where everyone can send a mail with the bugnumber in the subject line to get the status back, like internally not reproducable, internally fixed, open, duplicated with VB-xxx and so one

    IMO the lack of knowing what happend with the reported bug is a big annoyance for the users



  • @derday said in Where is the bug tracker?:

    I repeat a very nice idea, which someone wrote in one of the past blogposts:
    setup an autoresponder, where everyone can send a mail with the bugnumber in the subject line to get the status back, like internally not reproducable, internally fixed, open, duplicated with VB-xxx and so one

    The report this. Will be discussed internally.


    If you found a bug, please report the issue to the developers to fix it.

    How to do a bugreport for Vivaldi
    Report each bug separate at https://vivaldi.com/bugreport/
    Describe the issue as precise as you can.
    Add some information about extensions you use.
    Add information about the operating system and version you use.
    If you have problems with video or audio give us information about your installed codecs and graphics card/GPU.
    Add a exact link to the page where the issue comes up and can be tested.
    After reporting the issue, you will receive a confirmation mail from the bug tracker.
    In a reply to this mail you can add more information and files (like screenshots or testcases) as attachments and it will be added automatically to bug report.
    If you have questions about the bug please ask in forum first and do not forget to post the VB-XXXXX bug number (you can find it in confirmation mail).

    Thanks in advance for helping us to make Vivaldi better!




  • @gwen-dragon
    ok, done (VB-34514)


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.