| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Patch by Brad Baetz <bbaetz@student.usyd.edu.au>
r= jake, justdave
|
| |
|
|
|
|
|
|
| |
attachment to the bug you just created pointed at
the old attachment form instead of the new one.
Patch by Josh Soref <timeless@mac.com>
r= myk x2
|
| |
|
|
|
|
|
|
| |
shouldn't have been trusted, it was possible to file a
bug pretending to be someone else if you edited the HTML by hand before submitting.
Patch by Dave Miller <justdave@syndicomm.com>
r= bbaetz, jake
|
| |
|
|
|
|
|
| |
each others' cookies. Cookies now have a path value that can be set to indicate which bugzilla install they belong to. Browsers will only send the cookie to the appropriate installation. The path can be set in the 'cookiepath' parameter in editparams.cgi.
Patch by Dave Lawrence <dkl@redhat.com>
r= myk, justdave
|
| | |
|
| |
|
|
|
|
|
| |
instead of select widgets. Also, product groups are now only offered if they are either already set, or match the current product (i.e. the option to set a product bit for a product other than the one the bug is in is no longer available) This results in much less clutter for the admin folks on sites with lots of products.
Patch by Joe Robbins <jmrobins@tgix.com>
r= justdave@syndicomm.com
|
| |
|
|
|
|
|
| |
deleting it (prevent new bugs from being placed into that group, but don't remove the group restriction from bugs already in it).
Patch by Myk Melez <myk@mozilla.org>
r= justdave@syndicomm.com
|
| |
|
|
|
|
|
| |
give a long description, and the first person who added a comment had their comment become the long description of the bug.
Patch by <jake@acutex.net>
r= justdave
|
| |
|
|
| |
specified on the new bug form. This bug was introduced in the patch for bug 66876 (v1.29 of post_bug.cgi)
|
| |
|
|
| |
based on patch submitted by baulig@suse.de (Martin Baulig).
|
| |
|
|
|
|
|
|
|
|
| |
during bug entry. instead of trying to be really intelligent over what a valid
url field is, or doing any kind of complicated regexping and forcing http://
on everyone, what we do instead is pre-seed enter_bug.cgi bug_file_loc with http://
in the text field. if that is all there is in the field when we are in post_bug.cgi,
then the value gets set to null (no URL entered into the new bug form). this allows
for you to enter in any valid url that you want, but also make it obvious that
http:// should be there for http:// urls at bug entry time
|
| | |
|
| | |
|
| |
|
|
| |
longer given in show_bug.cgi to make bugs confidential. I need to change lounge so it no longer automatically updates.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
that all products have at least that milestone defined.
|
| |
|
|
|
|
|
| |
of a group per project, and automatically put new bugs against that
project into that group, thus allowing entire projects to be protected
against viewing by unauthorized users. This is all optional,
controlled by new parameters.
|
| |
|
|
| |
confidentiality when submitting a new bug.
|
| |
|
|
| |
have a universal (and more noticable) way of displaying them.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
"editbugs" and "canconfirm". People without these states are now much
more limited in what they can do.
For backwards compatability, by default all users will have the
editbugs and canconfirm bits on them. Installing this changes as is
should only have one major visible effect -- an UNCONFIRMED state
will appear in the query page. But no bugs will become in that state,
until you tweak some of the new voting-related parameters you'll find
when editing products.
|
| |
|
|
|
| |
table. There is now a separate entry for each new long description,
rather than appending them all together in one big field.
|
| |
|
|
|
|
|
| |
me. Added a footer to every page. Add some options to do things like
display checkboxes instead of scrolling lists, and a new formatting
for email diffs, and show list items capitalized instead of all upper
case.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
enter_bug.cgi does.
|
| |
|
|
|
|
| |
the change (after all, they are right there viewing things interactively).
To make this clear to everyone, print out the exact email list as each
bug is processed.
|
| | |
|
| |
|
|
|
| |
newline characters at the end, depending on the operating system of
the browser that submitted the text.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
