Closed
Bug 41712
Opened 26 years ago
Closed 24 years ago
It should be possible to turn off URL fields in bug reports
Categories
(Bugzilla :: Creating/Changing Bugs, enhancement, P3)
Bugzilla
Creating/Changing Bugs
Tracking
()
RESOLVED
DUPLICATE
of bug 372966
People
(Reporter: cdurst, Assigned: myk)
Details
Attachments
(2 files)
|
9.54 KB,
patch
|
Details | Diff | Splinter Review | |
|
9.54 KB,
patch
|
jouni
:
review-
|
Details | Diff | Splinter Review |
My company is considering using Bugzilla as our official bug tracking software,
however the "enter_bug" form seems very cluttered for our purposes.
Since our products have nothing to do with web browsing, the URL field of the
bug report is totally superfluous. It would be nice to be able to turn it off
from the edit parameters window.
I have already implemented this change on our local copy of Bugzilla and will
attach a patch for the current Bugzilla version (2.10) to this bug report. The
patch leaves the bug_file_loc field in the database (it is just left empty), and
if it is non-empty for some reason, it will still appear in any report or form
where it does now. In retrospect, it might have been nice if it was
controllable on a product-specific basis, but I don't yet know how to do
something like that.
Caveat: I believe my patch is correct and complete, however I am a relative
neophyte when it comes to writing Perl scripts.
In particular, I'm not sure whether the changes to the prettyasciimail format
stuff in "processmail" is implemented correctly.
| Reporter | ||
Comment 1•26 years ago
|
||
| Reporter | ||
Comment 2•26 years ago
|
||
Updated•25 years ago
|
Whiteboard: 2.14
Updated•25 years ago
|
Whiteboard: 2.14 → 2.16
Comment 6•25 years ago
|
||
-> Bugzilla product, Creating Bugs component, reassigning.
Assignee: justdave → myk
Component: Bugzilla → Creating/Changing Bugs
Keywords: review
Product: Webtools → Bugzilla
Whiteboard: 2.16
Version: other → unspecified
Comment 7•24 years ago
|
||
When we get templates all over, you can just remove it from the enter_bug and
show_bug templates, and you'll never see it again. So I suggest we don't
consider this patch.
Gerv
Comment 8•24 years ago
|
||
Everything isn't as simple as templates, Gerv. Some things provide an
automatically generated list of columns, eg change columns.
Comment 9•24 years ago
|
||
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut. Thus this is being retargetted at 2.18. If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Comment 10•24 years ago
|
||
Comment on attachment 11019 [details] [diff] [review]
This is an update of my patch to the latest CVS versions
Template stuff needed again, if this gets implemented.
See bug 62909 for more opinions on disabling single fields.
Attachment #11019 -
Flags: review-
Comment 11•24 years ago
|
||
Gerv marked the previously mentioned bug 62909 as WFM. The same argumentation
goes here, so unless somebody comes up with a nice easy-to-implement solution
for the time between now and the day custom fields land, I think this should be
WFMed as well.
Comment 12•24 years ago
|
||
Yep, WFM
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 13•24 years ago
|
||
clearing target in DUPLICATE/WORKSFORME/INVALID/WONTFIX bugs so they'll show up
as untriaged if they get reopened.
Target Milestone: Bugzilla 2.18 → ---
Comment 14•17 years ago
|
||
This bug is not WFM. Having to edit templates is not a good solution. This will be addressed by bug 372966.
Resolution: WORKSFORME → DUPLICATE
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•