Open Bug 302254 Opened 19 years ago Updated 17 years ago

Introduce the concept of "missing the boat" to flags - allow copy and move to take all pending flags to the new flag

Categories

(Bugzilla :: Attachments & Requests, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

()

People

(Reporter: timeless, Unassigned)

Details

so...
the concept of missing the boat makes perfect sense to people
and many train tickets are capable of dealing w/ it
some train tickets merely offer to automatically exchange
flags don't have this concept
i think they should...
i.e. i should be able to go to edit flags for 1.7.11 and say "anything that's
still pending is forked to a new flag 1.7.12
anything that's currently not pending keeps its current flag
currently what people have to do is 1. copy the flag, 2. minus/clear the
pendings. 3. rerequest for the new flag

justdave says: I do that with the documentation flags every time we branch with
Bugzilla :) everything pending for "documentation?" at the time we branch
automatically gets "documentation2.20?" (or whatever the appropriate flag for
the branch is)

so you actually have a distinction between copy and move. the exact wording is
subject to negotiation, but basically:
1. there needs to be a mode where the current flag is closed for new requests,
all pending requests are moved to the new flag which is equivalent except for
its name.
2. there needs to be a mode where the current flag is cloned to a new name, and
all pending requests for that flag are copied to the new flag with the new name.

the current clone flag feature is probably still useful, so some wordsmithing
will be required. at bmo i expect for branches (both suite, toolkit and
bugzilla) we'll be using this feature more than the current capabilities. (for
creating new kinds of flags, we'll probably use the current capabilities.)
You need to log in before you can comment on or make changes to this bug.