Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Using of Alias breaks "Depends on" Tree | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Rainer Bielefeld <rainerbielefeld_ooo_qa> |
Component: | Bugzilla | Assignee: | AOO issues mailing list <issues> |
Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | |
Severity: | Normal | ||
Priority: | P3 | CC: | issues, pescetti |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Rainer Bielefeld
2013-06-01 18:10:44 UTC
Might be a general Bugzilla bug? I'm not sure there is something wrong here (but I may miss something, especially on the "Alias" stuff). This is what I see: 1) In https://issues.apache.org/ooo/show_bug.cgi?id=121420 "Depends on" has 115 issues listed. This is expected. Apparently we've done a very good job here, since only 3 are still open and 112 are closed. 2) The "Show dependency tree" link leads to https://issues.apache.org/ooo/showdependencytree.cgi?id=121420&hide_resolved=1 that shows only the 3 open bugs, under the title "Bug 121420 depends on 3 open bugs". This seems fine too. 3) If I manually put "hide_resolved=0" in the URL, i.e., I open https://issues.apache.org/ooo/showdependencytree.cgi?id=121420&hide_resolved=0 then I see all the 115 bugs. The title changes to "Bug 121420 depends on 115 bugs". This seems fine too. I haven't bothered checking in the Bugzilla UI the way to get to the same list without manually editing the URL. Does this explain the behavior? I still can't see how the Alias fits in the picture, but the difference between #2 and #3 could be enough as an explanation. @Andrea Pescetti That's exactly the description. I simply remembered to have seen quite a lot of bugs in the tree some time ago, after the "alias" change (what has no influence at all) I tried again and saw the few remaining bugs in the tree. Was afraid that I had broken something instead of simply reading the URL Thx for investigation, so INVALID! |