Author: EMU (Huang Xiwei)
Bugzilla 2.19.2 Trial
Bugzilla 2.19 Trial version has been released for a long time. But we continue to use 2.18, one is not known whether the 2.19 version is stable, and the second is that the 2.18 version of the WFIFI's Chinese template can be used. But now the company began to assess whether to buy Jira. So rough compare JIRA and BUGZILLA.
I saw JIRA, and Bugzilla had a featured, and it was a more prominent feeling: 1 Jira is an IMS (Issue Management System), that is, it can manage BUG, but also manage other types of ISSUE such as Task. And you can create new types of ISSUE. In contrast, Bugzilla is a DMS (Defect Management System), and everything in its eyes is bug. Although there is no big difference in the event that can be achieved, but it feels the difference between them. 2 JIRA supports Subscribe, which is to subscribe to the specified bug information, and the bugzilla to version 2.18 has not found such a function. 3 Bugzilla supports Generation Chart, JIRA does not seem to have this feature. 4 Bugzilla now has a Chinese package, and Jira supports about 8 species, no Chinese is found. However, as a foreign company, we don't need an interface of Hanhua DMS5 JIRA's enterprise version is said to define your ISSUE's handling process, but it seems to be changed to the source code. 6 JIRA's permission system is made detailed than Bugzilla. 7 Jira to spend Money
In order to more fair comparison Bugzilla and Jira, the Internet was shocked by the latest Bugzilla2.19.2, which is not much more characteristic than its 2.19.1, but it is said to change some bugs. Compared with the 2.18 version, the most prominent is to add a function similar to JIRA's subscribe, called WhiNing. In addition, the username will be pulled down, and you can do it without knocking Assignee (in fact, I have already achieved the same function, my QA is actually how to knockerel, and the conditions that generate reports can be reversed. There is also a characteristic that writes environment variables and report parameters looks not big. But the first Note didn't understand:
A higher level of categorization (departments, locals, etc ...) is now Available for Bug Reports
This should be a more advanced classification when it is said to be Report? But in the bug associated with it:
IT Would Be Nice if One Could Group Products Into Categories (Departmentments, Groups, Organization, ETC.) ...
This should be the meaning of categorizing when creating products.
Because it has been installed on the server, it is easy to install 2.19. Enjoy a newbugzilla directory in the Apache's publishing directory, press the downloaded package to go. Then, in the order of command, Perl checksetup.pl, verify that all the packages are all striking and generate the localconfig file. Open LocalConfig, fill in $ db_pass, re-checksetup.pl. Installing scripts Start Upgrade Database (New version of Bugzilla needs to use some new tables or add some new fields in the old table), smooth pass.
Open the browser to access Newbugzilla, in addition to doing everything else in the Chinese interface, go in to see Assignee or the text box, the Whiheng function can not find, strange. Go to the directory search related files, found Whine.pl in the root directory. Since there is no link, you will directly knock the address to access it? Enter its address from IE, come out for an error page: no permission. The original new feature is to be associated with new groups. Entering users to add all the characters first. Go back to the home page to refresh, really, come on a whiteing link, click to see, cool! The problem of the username drop-down box is associated with a bug above the release notes of version 2.19.1. In the past, see this bug's instructions and attachments, saying that it is to add a code in / template / en / default / global, called UserSelect Ottml.tmpl. Located locally, this file is already, but why didn't the user become a drop-down list? Open userSelect.html.tmpl look at: [% IF Param ("UseMenuforusers")%] ...... It turns out that used UseMenuForusers This parameter is really displayed as drop-down box. Inside the parameter, find UseMenuforusers, change to TRUE, return to the created bug page, the user box really turns down the box.
Find some of the a higher level of categorization? I didn't find something like Categories for a long time, but I found a new thing in Parameter: useclassification. After opening this parameter (ON), the menu has more classification, probably what this thing is. Product classification can be established in Classifications, and then build products in the product class, or associate the old products to the created classification (all of which are not associated are all unclassified classes). This will choose to classify, then select the product, then select the component. Such functions are still a bit discussion for units that are more complicated to the product line.
Author: EMU (Huang Xiwei)
