Closed
Bug 271984
Opened 20 years ago
Closed 19 years ago
Default milestone should be a <select>, not a text entry.
Categories
(Bugzilla :: Administration, task)
Bugzilla
Administration
Tracking
()
RESOLVED
FIXED
Bugzilla 3.0
People
(Reporter: kiko, Assigned: remi_zara)
Details
Attachments
(1 file, 2 obsolete files)
1.26 KB,
patch
|
LpSolit
:
review+
|
Details | Diff | Splinter Review |
The product's default milestone is currently a text entry; this is unreasonable
given that milestones are a bound list specified per-product. Consensus on
developers@ is that it be moved to a <select> menu.
Updated•20 years ago
|
Target Milestone: --- → Bugzilla 2.22
Updated•19 years ago
|
Assignee: kiko → administration
Severity: normal → enhancement
OS: Linux → All
QA Contact: mattyt-bugzilla → default-qa
Hardware: PC → All
Target Milestone: Bugzilla 2.22 → Bugzilla 2.24
Updated•19 years ago
|
Whiteboard: [Good Intro Bug]
Updated•19 years ago
|
Assignee: administration → bugzilla-mozilla
Attachment #212355 -
Flags: review?(kiko)
Comment 2•19 years ago
|
||
Comment on attachment 212355 [details] [diff] [review]
make the default milestone a <select>
>Index: template/en/default/admin/products/edit-common.html.tmpl
>+ <option [% "selected=\"selected\"" IF m.name == product.defaultmilestone %]>
>+ [%- m.name FILTER html -%]</option>
The <option> must have a 'value' attribute.
>+ [% ELSE %]
>+ <font color="red">missing</font>
>+ [% END %]
Nit: fix the indentation of <font> (2 whitespaces for templates).
Attachment #212355 -
Flags: review?(kiko) → review-
Addressed comments
Attachment #212355 -
Attachment is obsolete: true
Attachment #212356 -
Flags: review?(LpSolit)
Comment 4•19 years ago
|
||
Comment on attachment 212356 [details] [diff] [review]
patch v1.1
>+ [% IF product.milestones.size %]
>+ <select name="defaultmilestone">
>+ [% FOREACH m = product.milestones %]
Nit: [% FOREACH %] should not be aligned with <select> (indentation).
>+ [% ELSE %]
>+ <font color="red">missing</font>
>+ [% END %]
When adding a new product, I can no longer set the default milestone. In this case, you should offer a text box (as it does actually) instead of displaying this message.
Attachment #212356 -
Flags: review?(LpSolit) → review-
Comment 5•19 years ago
|
||
bkor, I'm reassigning the bug to remi as he is working on it (he is a newbie, and thought the bug was assigned to the default assignee because its status was NEW instead of ASSIGNED).
Assignee: bugzilla-mozilla → remi_zara
Addressed comments.
It is strange though that you can choose a not yet existant milestone as the default. I guess that the fact that there was no foreign keys in MySQL helps :)
Attachment #212356 -
Attachment is obsolete: true
Attachment #212357 -
Flags: review?(LpSolit)
Comment 7•19 years ago
|
||
(In reply to comment #6)
> It is strange though that you can choose a not yet existant milestone as the
> default. I guess that the fact that there was no foreign keys in MySQL helps
The reason you can choose a milestone when creating a new product is that this milestone will be added to the miletones table as well, so there is no referential integrity problem. But as soon as the product is created, it doesn't let you create new milestones from here anymore and you have to go to editmilestones.cgi to add new ones.
Status: NEW → ASSIGNED
Comment 8•19 years ago
|
||
Comment on attachment 212357 [details] [diff] [review]
patch v1.2
Works great! Thanks for the patch. r=LpSolit
Attachment #212357 -
Flags: review?(LpSolit) → review+
Updated•19 years ago
|
Flags: approval?
Whiteboard: [Good Intro Bug]
Updated•19 years ago
|
Flags: approval? → approval+
Comment 9•19 years ago
|
||
Checking in template/en/default/admin/products/edit-common.html.tmpl;
/cvsroot/mozilla/webtools/bugzilla/template/en/default/admin/products/edit-common.html.tmpl,v <-- edit-common.html.tmpl
new revision: 1.5; previous revision: 1.4
done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•