Closed Bug 343853 Opened 20 years ago Closed 17 years ago

offer a way to merge two flags

Categories

(Bugzilla :: Attachments & Requests, enhancement, P4)

2.20.1
enhancement

Tracking

()

RESOLVED DUPLICATE of bug 290755

People

(Reporter: timeless, Unassigned)

Details

minor note: currently bmo has about half a dozen review flags, most are really the same functionally, but for historical reasons they're distinct, this frequently causes pain. i'd like to be able to merge a flag (flag-going-out-of-style) into another flag (survivor-flag) using the editflagtypes ui so that i could consolidate flags w/o losing flag data. expected behaviors: (option 1): editing flag-going-out-of-style offers an option: merge all instances of this flag type into: [list-of-all-other-compatible-flags|v] (option 2): editing survivor-flag offers an option: annex this flag type: [list-of-all-other-compatible-flags|v] option 2 as worded here definitely sounds awkward. the result: 1. all inclusions from both are listed. any exclusion from flag-going-out-of-style that directly conflicts w. an inclusion in survivor-flag is listed in a box: exclusion rules from flag-going-out-of-style that conflicted with rules from survivor-flag: ._________________________. | | | ... | |_________________________| exclusion rules from survivor-flag that conflicted with rules from flag-going-out-of-style: ._________________________. | | | ... | |_________________________| merged inclusion rules: .__________________________________________________. | Product1:__ALL__ (from surivor-flag) | | Product2:__ALL__ (from flag-going-out-of-style) | | Product3:__ALL__ (listed in both flags) | | ... | |__________________________________________________| the labels should include a hint as above indicating which place provided a given inclusion. Rules in the list should be sorted alphabetically (not in some random definition order).
OS: Windows XP → All
Priority: -- → P4
Hardware: PC → All
Same request as bug 290755, where the original and target flag names are the same.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.