|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | Handling DUPLICATE issues | ||
|---|---|---|---|
| Product: | Infrastructure | Reporter: | oblomov <gip.bilotta> |
| Component: | Bugzilla | Assignee: | Unknown <non-migrated> |
| Status: | CLOSED FIXED | QA Contact: | issues@www <issues> |
| Severity: | Trivial | ||
| Priority: | P3 | CC: | issues, maison.godard, stx123 |
| Version: | current | ||
| Target Milestone: | CEE 5.2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
|
Description
oblomov
2003-11-16 23:04:34 UTC
*** This issue has been confirmed by popular vote. *** *** Issue 22825 has been marked as a duplicate of this issue. *** adding myself to CC When you marked 22825 as a duplicate, did you transfer the votes? I personally find it reprehensibly irresponsible to do anything else. Hi Robert, sorry ! I don't understand your question The 22825 is an issue i just created and were there were no vote But in fact you ask me if i transfered when i duplicate !! this is exactly what this issue deals with Is there any hint to report the Votes from one issue to an other i have to know ? thanks Laurent I don't understand all parts of the initial description. I don't think that duplicating the comments is useful. Furthermore an issue is not closed if marked as duplicate. It's RESOLVED with the resolution "DUPLICATE" and should be verified before final closure. But I think the following data should be "cloned" - votes (up to the limit for each user) - duplicates Reassigning to support. Hi Stefan, As I understand this issue, you would like the votes to auto populate to duplicate issue in IZ. I spoke to engineering about this enhancement request. Right now Collab is focusing resources on Project Tracker & not on complex enhancements to IZ beyond serious maintence. Closing this as wont fix for now. Eric Hi Eric, Yes, your understanding of the issue is correct. I'm not bound to IssueTracker (aka IssueZilla) for this issue. It's fine with me, if you take it into consideration for PT. Thanks, Stefan I created pcn 28394 to monitor this request for enhancement, Eric Moving this issue to RESOLVED->LATER statuts. Reopening this issue. Mistakenly marked this as RESOLVED->LATER. Will follow up with engineering regarding this. CollabNet is not planning to do this level of enhancement in IZ. However, there is strong possibility to include this when we implement voting in Project Tracker. Marking this as RESOLVED->REMIND *** Issue 56565 has been marked as a duplicate of this issue. *** *** Issue 56564 has been marked as a duplicate of this issue. *** *** Issue 56564 has been marked as a duplicate of this issue. *** *** Issue 57393 has been marked as a duplicate of this issue. *** *** Issue 65006 has been marked as a duplicate of this issue. *** *** Issue 65006 has been marked as a duplicate of this issue. *** Reopening to change/update the current status of the issue . Hi, We will try to consider this request in Project Tracker if OpenOffice decides to move to PT. Marking as RESOLVED -> LATER. Thanks, Jeeva Support Operations Considering this issue was opened THREE YEARS AGO - Marking it "Later" now just shows how this shit will never get fixed. I do not understand why resolution is set to "resolved". Please refer to http://qa.openoffice.org/scdocs/issue_lifecycle.html. The "RESOLVED" status is to be used when the target system (here, issuezilla) is modified, and awaiting verification. In other words, this resolution means that all possible actions are already taken; and nothing needs to be done further if everything goes well. But is that so? All that Jeeva offers is to "consider it" **IF** OOo migrates from IssueZilla to Project Tracker. That's two remote possibilities rolled into one! OK let us pretend that those two actions WILL happen in future. Even then, does this issue deserve a "Resolved" status TODAY? I think Jeeva just handed a death sentence to it. Sadly, Sun/OOo staff sweeps maximum possible issues under carpet like this; and I don't see a voice of sanity who calls out a halt to this madness. The correct process is to keep the issue OPEN and forward it to the policymaker who decides whether to migrate to Project Tracker. *** Issue 65006 has been marked as a duplicate of this issue. *** @raindrops: The status resolved/later is not a valid status for issues for the OpenOffice.org product. This status is only used for issues regarding the collab.net infrastructure if issues has been solved for a CEE release which has not been applied yet to the OpenOffice.org website infrastructure. That's exactly my point: Is a new feature added to Issuezilla, which solves this problem? At this point of time, it may be under testing. If that has NOT happened, then it is NOT resolved. CollabNet Support is currently reviewing the issues under Resolved-Later. If the issues are fixed currently in any of the present CEE releases, then it will be marked as Resolved-Fixed. There might be a few issues which might not be in our future roadmaps which might be closed as Wontfix unless it does not lie under any custom request. *** Issue 84534 has been marked as a duplicate of this issue. *** When changing an issues component, all existing votes were automatically removed. In CEE 5.2 P1,now there is an option so that the votes can be preserved 1-Precondition: Set 'remove votes' - 'ON' under 'Issue organization' section' of 'Edit advanced configuration options (edit setting)' page under 'configuration options' page and save settings. Observations: All the votes are removed when the user changed the component to something else. And the respective votes received email notification about the removal of votes on the issue. 2-Precondition: Set 'remove votes' - 'OFF' and save the setting under 'Edit advanced configuration options (edit setting)' page under 'configuration options' link. Observed: All the votes count are remaining the same even after changing the component to something else. Regards, Ramya Support Operations |