Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Correct openoffice.org Issuezilla Component Label | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Unknown <non-migrated> |
Component: | Bugzilla | Assignee: | Unknown <non-migrated> |
Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P2 | CC: | issues, michael.bemmer |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
URL: | http://www.openoffice.org/issues/enter_bug.cgi?product=www | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2000-10-23 18:17:15 UTC
huh? what's wrong with IssueZilla? vs Issuezilla this must be a test issue because it appears invalid or perhaps nitpicky. If given the choice between calling it "Issuezilla" and "IssueZilla", i prefer the latter. about the only places it says Issuezilla in this program, inconsistently is due to the result of the "bug" --> "issue" tags-query-replace i ran... feel free to reopen if you want to suggest i try to make the name more consistent inside issuezilla itself. Niels, I don't care about this issue anymore, but I wouldn't have to re-open it because it's not closed. I think it's a little user interface problem that one is not really aware that a bug is not closed, could be more transparent. I previously resolved the issue as "resolved invalid". If you want to close the issue then select "mark issue as CLOSED" and commit. i agree that IssueZilla is lacking good UI design. We'll have to wait for scarab, as we're not going to be doing UI/usability changes to IssueZilla. It's just an interim solution. It's not really a UI issue, more a matter of defining and sticking to the workflow. I thought if you rejected a fix, you'd then close an issue. But maybe it's a better workflow to wait for a response and let the person who requested the fix close it. Anyways, I close it now. |