|
Bugzilla – Full Text Bug Listing |
| Summary: | Login to this stupid bugzilla is completely broken | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE.org | Reporter: | teo teo <php4fan> |
| Component: | Bugzilla | Assignee: | Martin Caj <mcaj> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <novbugzilla-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | Andreas.Stieger |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
teo teo
2022-06-06 18:16:48 UTC
Hi Martin, would you please help to take a look at this issue? I'm not sure whether it is correct to assign it to you, please feel free to reassign whenever necessary, thanks. Which browser(s)??? Could this be one of those situations where clearing all bugzilla cookies before attempting login clears the problem? > Which browser(s)??? Chrome on Linux. (but I'd be surprised if it made a difference) > Could this be one of those situations where clearing > all bugzilla cookies before attempting login clears the problem? It could be, in part. At some point I was able to log in after clearing cookies, and I thought that was the definitive workaround. But then it also happened to me that clearing cookies didn't help. Another thing that seemed to help (but I'm not so sure, it could be random), maybe in combination with clearing cookies, was to go to https://bugzilla.opensuse.org/index.cgi?GoAheadAndLogIn=1 and NOT use the embedded login form that is found in other pages. > Login to this stupid bugzilla is completely broken Looking at multiple of your bugs... You seem to have a complete and utter lack of ability to search for existing reports, file separate issues with cross-references for context, or even do some basic research about the part you have in causing the breakages... I think you have long overstayed your welcome. In any case, resolving as duplicate of bug 1194193 which you should have seen already. *** This bug has been marked as a duplicate of bug 1194193 *** > You seem to have a complete and utter lack of ability to search for existing reports
Not ability, willingness.
In decent bug trackers, after you type the title and the description (whether it is upon submitting or it gets updated in real time as you type), a list of potentially similar bugs is shown.
When that happens, I do check them thoroughly.
If the people maintaining the code don't care enough to install bug tracking software that automates trivial (but tedious) tasks that can be automated, they're gonna have to deal with duplicate reports from time to time.
Also, when I do try to do a search on my own and the search engine is garbage, I won't ever use it again.
Search box is right on top, in addition to "Possible duplicates" when failing a new bug. But thank you for confirming you are unwilling. > in addition to "Possible duplicates" when failing a new bug Right, my bad, this is one of the bug trackers that does have that. Then I didn't find one that looked related. I assure you, when a list of related bugs shows up I check. I can definitely miss one, honest mistake. > Search box is right on top The search engine _is_ crap, so that one I definitely didn't waste time trying. |