Open
Bug 190822
Opened 22 years ago
Updated 12 years ago
link parameters with documentation
Categories
(Bugzilla :: Administration, task)
Tracking
()
NEW
People
(Reporter: hauser, Unassigned)
References
()
Details
For example, I see "usebuggroups" and a sentence that is too short to really tell me what this feature is all about. Therefore, I suggest to link this bold "usebuggroups" (target=_new?) with http://www.bugzilla.org/docs216/html/groups.html or/and http://www.bugzilla.org/docs216/html/parameters.html or rather %version% instead of "216" ... (e.g. as a "more documentation" button at the end of the sentence). Adding similar links back into the documentation in http://bugzilla.mozilla.org/editgroups.cgi wouldn't hurt either.
Comment 1•22 years ago
|
||
The "usebuggroups" param no longer exists on the tip. I do like this idea however. :) params could certainly be linked to the copy of the docs that ships with Bugzilla (since it's in the same tree with it), without having to have an outside connection to the Internet from that server's network or needing to know the version number.
Depends on: 46296
Target Milestone: --- → Bugzilla 2.18
Comment 2•20 years ago
|
||
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 3•20 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Comment 4•19 years ago
|
||
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
Assignee: justdave → administration
QA Contact: mattyt-bugzilla → default-qa
This would really be great for those struggling to set up a new Bugzilla system. Even better would be to link to a local copy of the documentation. Is one automatically provided with Bugzilla?
Comment 6•19 years ago
|
||
Cf. bug 316127. Maybe we can use the infrastructure provided there as well. I'm putting it up as a blocker. I don't think we can make it happen for 2.22, though.
Depends on: 316127
Target Milestone: Bugzilla 2.22 → Bugzilla 2.24
Comment 7•18 years ago
|
||
We are freezing the code for 3.0 in two weeks and we don't expect this bug to be fixed on time.
Target Milestone: Bugzilla 3.0 → ---
Comment 8•12 years ago
|
||
We already have a Help link in the header of the page which points to the documentation. I'm not sure we need more than that. The short description should be explicit enough.
You need to log in
before you can comment on or make changes to this bug.
Description
•