Closed
Bug 98464
Opened 23 years ago
Closed 18 years ago
"Bugs this conflicts with" list
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 287334
People
(Reporter: gwalla, Unassigned)
Details
(Whiteboard: [relations:other])
It might be useful to have a list of bugs (like the "depends on" and "blocks"
lists) for bugs that have mutually exclusive potential resolutions. This would
probably be used mostly with feature requests, but would probably also get used
for UI issues.
Comment 1•23 years ago
|
||
Ooh, I like this. This would really come in handy now and again for patch
triage... If a patch is written for this before 2.16 ships I'll bump it to
2.16. For now, most enhancements are going to 2.18
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.18
Version: 2.10 → 2.15
Updated•23 years ago
|
Whiteboard: [relations:other]
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 → create-and-change
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•