To fix this potential problem, the Details page always displays the HTML source instead and users can see rendered page by clicking on View. Flags: Changing the requestee of a flag no longer changes the requester. Reports: If JavaScript is enabled in your web browser, tabular reports are now sortable based on any displayed column.
Dependency graphs: The Show every bug in the system with dependencies option has been removed. Searches: The columns displayed by default in buglists have changed. These columns are now displayed by default unless otherwise specified: product component assignee bug status resolution bug summary last change date This means that the priority, severity and operating system columns are no longer displayed by default.
Searches: Buglists will now only display the first bugs by default. It is still possible to display the whole list, though. Searches: When using relative dates and times, -1w is now a synonym for -7d and means exactly 7 days.
Previously, -1w meant the beginning of the week, which was confusing some users. The same confusion existed for -1d which was different from h , and for -1m which was different from d. Now if you really want the beginning of the day, week or month, you must use -1ds , -1ws , and -1ms respectively, where "s" means "start of". This change will affect existing saved searches using relative dates. Searches: A new Include fulltext when performing quick searches user preference has been added which permits users to include or exclude comments when using quicksearches.
Searches: It is now possible to query for bugs based on personal tags in the Custom Search section in the Advanced Search page. Email notifications: The date and time of comments are no longer displayed in the comment header in bugmails. This information is already available in the email header itself. Enhancements for Administrators and Developers Installation: checksetup.
Security: Bugzilla 4. This is particularly useful for large installations with several tens of thousands bugs where returning all bugs doesn't make sense and would have a performance impact on the database.
The user can ask to see a larger list, though. This is a hard limit and a user cannot bypass this value. This parameter should only be disabled if your installation is unable to support the load generated by this feature. Flags: Users with local editcomponents privileges can now edit flag types for products they can administer.
Till now, you had to be in the admin group to do that. WebService Changes Two new methods have been added: Product. It now simply ignores this empty value. In Bug. Outstanding Issues Bug : When changing multiple bugs at the same time, there is no "mid-air collision" protection. Bug : The support for restricting access to particular Categories of New Charts is not complete.
You should treat the chartgroup parameter as the only access mechanism available. Bug : When viewing a bug, WebKit-based browsers can automatically reset a field's selected value when the field has disabled values. This means bugmails are now fully localizable. YUI has been upgraded to 2. As announced in the release notes of Bugzilla 4. This script is no longer useful since Bugzilla 3. This script didn't work for a long time. In Bugzilla 4. Bug Moving several bugs at once into another product displayed the same confirmation page again and again, and changes were never committed regressed in 4.
Bug Marking a bug as a duplicate now works in Internet Explorer 9. Bug importxml. Bug Data entered while reporting a new bug could be lost if you had to click the "Back" button of your web browser. Bug WebServices methods will return undefined bug fields as undefined instead of as an empty string. This change is consistent with how Bugzilla 4. Bug LWP 6. When installing this module using install-module. Bug Viewing a bug report should be significantly faster when your installation has many custom fields.
Bug 4. Now, when using install-module. If you are currently experiencing this bug and it prevented you from installing 4. Bug Email notifications about dependencies and flags had the wrong timestamp. Bug Autcomplete for users now works even if you are using the "emailsuffix" option. Bug Javascript errors during series creation in New Charts have been fixed. Bug The "Show Votes" page now works, for installations using the Voting extension. Bug Minimum Requirements Any requirements that are new since 3.
New Attachment Details UI The UI used for editing attachment details has been completely redesigned, allowing for a normally-size comment box to be used when commenting on attachments, and allowing nearly the entire screen width to be used when doing code reviews or editing an attachment as a comment.
Autocomplete for Users and Keywords Once you type at least three characters in any field that can contain a user including the CC, QA Contact, or Assignee fields , a list will appear containing all of the users whose real names or usernames match what you are typing.
General Usability Improvements In addition to the enhancements listed above, there have been many improvements made across the Bugzilla user interface. Saved a lot of time. Thank you. Any chance for a subversion install in the near future? Thanks for the step-by-step guide.
It was good. I had a problem with Centos 5. The problem was solved by different configuration in the httpd. AddHandler cgi-script. The step by step guide was really helpful. Firstly I was not able to install ImageMagick no matter what I tried. Like you mentioned above I have installed the various packages at the cpan prompt. I install each one and then restart httpd and something else is missing.
Hello, first of all i would like to say that the article is a very good one. The http service will fail a no. Each time the service fails check the error it is throwing. Every you get this check the module that it cannot locate and install it from the cpan prompt.
After a no. Even then I was not able to view the Bugzilla home page through the browser. Again install each missing module from the cpan prompt. If everything goes well all dependencies should be resolved and you should be able to view the Bugzilla home page.
There some thing to be done at the end of installation….. Does this apply with Ubuntu Server 32bits?? PL line 5. Falling back to other methods to determine prerequisities. When trying to find httpd. The only httpd. Above steps are really great and in detail however, Can some one give me step by step details to install the Bugzilla on CentOS linux. Please tell me where this file can found. Checking for DateTime v0.
You probably need to run checksetup. Thanks in advance. Hi Ramesh, I have installed the latest version of bugzilla 4. After adding below lines in httd. I am on my CentOS. This step by step guide is very simple and has made me and easy task for installing the bugzilla on my centos. I have one major issue, I have executed all the 17 steps correctly. All the mandatory perl modules and optional perl modules are also installed.
I am not getting the bugzilla UI. Could anyone please help me to come out of this. I am struggling since last 3 to 4 days. Hi Ramesh, Could you please tell me the steps about setting up email configuration using SMTP for sending new account invitation.
I have done this by changing the following parameters in Bugzilla Administration page:. With the above email configuration, it will display that the new account invitation is sent to username mydomain. But the corresponding user is not receiving any mail from bugzilla mydomain. I am using centos 6. I am setting up sending the Emails to all the persons who are in the cc list and the watch list, whenever there is a change in the bug or a new bug is raised.
But I am getting the following error. Is there any problem with our bugzilla setup or is there any problem with the SMTP services of the hosting site. Compilation failed in require at eval line 3, line Dear all. Nice article. Do you have the correct username and password selected in localconfig? Great tutorial! I was wondering if you could possibly help me though.
This was due to the fact that ApacheSizeLimit was not installed properly. But when I install it I get the below error. Hi Tim, Were you able to figure this one out? I seem to be having the exact same problem with bugzilla 4.
Same thing: I am unable to attach files. Just like you I had upped Maxattachmentsize and Maxlocalattachment. For kicks changed permissions to Still no luck.
Thanks, Mike. Guten Tag reg Konqueror's error was a little difference. Guten Tag dazzed, am Mittwoch, Once you have place the Bugzilla source code under the web root directory, you can now check if any required perl module is missing by executing the command below;. Rerun the checksetup. Once the Bugzilla is done, you are then asked to set the Bugzilla admin email and name and password. To be able to access Bugzilla web interface, you need to create its Apache site configuration file.
Once you are done with the installation and setup of Bugzilla on Ubuntu You can then login using the administrator email and password you created above. You can as well create new accounts. Navigate through the Bugzilla and manage your application bugs. That brings us to the end of our tutorial on how to install Bugzilla bug tracker on Ubuntu
0コメント