272480 - Left over field_descs.* in change-columns should be in field-descs

Status: RESOLVED FIXED

(Bugzilla :: Query/Bug List, defect)

Description

[Shane H. W. Travis]

According to CVS Blame, most of the field_descs were moved out of change-
columns.html.tmpl and into field-descs.none.tmpl as part of bug 176461.

Inexplicably (to me, anyway) all the realname fields, plus a couple of others, 
were left in change-columns instead of being moved. This put me in the annoying 
situation this afternoon of changing 'Assignee' to 'Owner' as a field_desc, but 
then still having it show up as 'Assignee Realname' in colchange.cgi. Yeah, 
didn't take long to track it down, but I can't think of any good reason why 
these things should be separated, as it will lead to more mistakes like the one 
I made, and require customization of more templates for no good reason.

Dave, if there *is* no good reason, please confirm as NEW and assign to me, and 
I'll move them over. Thanks.

Comment 1

[Dave Miller [:justdave]]

sounds reasonable to me

Comment 2

[Frédéric Buclin]

This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".

Comment 3

[Max Kanat-Alexander]

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.

Comment 4

[Frédéric Buclin]

Fixed by bug 545587.