Open
Bug 127871
Opened 23 years ago
Updated 5 months ago
support for moving bugs to multiple installations
Categories
(Bugzilla :: Bug Import/Export & Moving, enhancement, P1)
Tracking
()
NEW
People
(Reporter: myk, Unassigned)
References
(Blocks 2 open bugs)
Details
Bugzilla should support moving bugs to multiple installations instead of just a
single one. This entails moving the moving configuration from editparams.cgi to
its own CGI, storing the configuration in the database (probably), and modifying
the UI so movers can specify to which installation they would like to move the bug.
Comment 1•23 years ago
|
||
This will be easier after the groups stuff, won't it? Then you can have an admin
group of CanMoveBugscape, CanMoveBugzillaOrg, where Bugscape and BugzillaOrg are
the short names in the mythical new 'move' table.
Updated•23 years ago
|
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.18
Updated•22 years ago
|
Component: Creating/Changing Bugs → Bug Import/Export & Moving
Comment 2•21 years ago
|
||
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
Comment 3•20 years ago
|
||
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 → import-export
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
Updated•18 years ago
|
Whiteboard: [roadmap: 3.2]
Updated•18 years ago
|
Whiteboard: [roadmap: 3.2]
Target Milestone: --- → Bugzilla 3.2
Updated•18 years ago
|
Priority: P2 → P1
Comment 4•17 years ago
|
||
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.
This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.
Target Milestone: Bugzilla 3.2 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•