Closed
Bug 616453
Opened 14 years ago
Closed 13 years ago
Changes to allow addition/removal of descriptions of statuses and resolutions
Categories
(Bugzilla :: Bugzilla-General, enhancement)
Tracking
()
RESOLVED
FIXED
Bugzilla 4.2
People
(Reporter: gerv, Assigned: gerv)
Details
Attachments
(1 file)
5.27 KB,
patch
|
mkanat
:
review+
|
Details | Diff | Splinter Review |
[This bug is to suggest a b.m.o. customization/fix for upstreaming. If it is approved, I will create and attach a proper patch.] People can add and remove statuses and resolutions, but there's no good way to add and remove the descriptions in the fields.html.tmpl page.cgi page, which describes what the statuses and resolutions are for. I suggest: a) Hooks to add statuses and resolutions to the relevant <dl>s. b) classes on the <dt>s and <dd>s so they can be hidden with CSS for statuses and resolutions which have been removed. Gerv
Updated•14 years ago
|
Severity: normal → enhancement
Assignee | ||
Comment 1•13 years ago
|
||
This seems like the right way. The CSS classes should stay the same even if the descriptions change. Gerv
Comment 2•13 years ago
|
||
Comment on attachment 507409 [details] [diff] [review] Patch v.1 Yeah, that looks like a totally good idea.
Attachment #507409 -
Flags: review?(mkanat) → review+
Updated•13 years ago
|
Flags: approval+
Target Milestone: --- → Bugzilla 4.2
Assignee | ||
Comment 3•13 years ago
|
||
Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/trunk/ modified template/en/default/pages/fields.html.tmpl Committed revision 7681. Gerv
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 4•13 years ago
|
||
mkanat: any chance of approving this for 4.0? The patch applies cleanly, and we could really use one of these hooks on b.m.o. (adding resolutions). Also, it would make it cleaner for us to fix bug 620753. Gerv
Assignee | ||
Updated•13 years ago
|
Flags: approval4.0?
Updated•13 years ago
|
Target Milestone: Bugzilla 4.2 → Bugzilla 4.0
Comment 5•13 years ago
|
||
Ah, no, but you can backport it. I don't want to add new CSS classes that are named that generically right before the release; there's always some chance they could cause a regression that we're not aware of.
Flags: approval4.0? → approval4.0-
Updated•13 years ago
|
Target Milestone: Bugzilla 4.0 → Bugzilla 4.2
You need to log in
before you can comment on or make changes to this bug.
Description
•