Community
Participate
Working Groups
When Orion was part of the e4 project, it used the bugzilla component e4 > Orion. After graduation Orion is a separate bugzilla product, and we move all open bugs over to the new bucket. Can webmaster remove the e4 > Orion component completely, moving all resolved bugs over to Orion > Client? We are still getting users regularly reporting bugs in the old place, so eliminating that component would simplify matters. I guess an alternative would be to rename the e4 bugzilla component to something like "Orion (Deprecated - report bugs against Orion product)"
Done. -M.
Matt, a problem has come up with this... We didn't have all the old target milestones in the new component, so when the bugs were moved over, we lost all the target milestones. We use that field to know what release the bug is fixed in. Would it be possible for you to hammer all those to have a "0.2" target milestone? I would happily do it, but I don't want to inflict the thousands of bugzilla emails on people. Basically any FIXED bug with no target milestone should be "0.2".
Just to confirm: You want me to set all 755 bugs with a target milestone of '---' and a status of 'FIXED' to a target milestone of '0.2' . -M
Yes please!