Open Bug 134761 Opened 18 years ago Updated 5 years ago
It should be possible for a bug in one Bugzilla installation to be marked a duplicate of a bug in another Bugzilla installation. This would make it possible to track duplicates between projects that share code but are tracked on different Bugzilla installations.
Severity: normal → enhancement
Priority: P4 → P2
Target Milestone: Future → Bugzilla 2.18
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee: myk → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
Assignee: create-and-change → extension.ideas
Component: Creating/Changing Bugs → Extension Ideas
You need to log in before you can comment on or make changes to this bug.