![]() The important part is to have enough RAM (4 GB or more recommended) and a fast processor (for instance, 3 GHz). For small teams (up to a few tens of users) with few bugs (up to a few thousands bugs), any good machine will do the job pretty well. The hardware requirements depend heavily on the size of the user base and on the number of bugs in your database. Linux is highly recommended and is our 1st-class citizen operating system. This means that Bugzilla can be installed on any platform where Perl can be installed, including Windows, Linux, and Mac OS X. To install and run Bugzilla on your server, the core requirement is to have Perl installed. Bugzilla sets the power in an individual’s hand to improve the value of business while providing a usable framework for natural attention to detail and knowledge store to flourish. It is now the most precious defect-tracking system against which all the others are measured. As a result, Bugzilla quickly became a favorite among the open-source users, due to its genesis in the open-source browser project with Mozilla. Most commercial and defect-tracking software vendors charged enormous licensing fees in the starting days of Bugzilla. It can dramatically increase the productivity and accountability of an individual by providing a documented workflow and positive feedback for good performance.Bugzilla provides a powerful, easy to use solution to configuration management and replication problems.Bugzilla can be used as a Test Management tool since it can be easily linked with other test case management tools like Quality Centre, ALM, Testlink ,.Later, Bugzilla was written in PERL and it uses the MYSQL database.It was written by Terry Weissman in TCL programming language in 1998.It helps the developers and other stakeholders to keep track of unresolved glitches with the product. Bugzilla is an open-source tool used to track bugs and issues of a project or a software. It is an extensively used as a bug-reporting device for all sorts of testing functions. I am getting following error while posting comment -> "You are not permitted to edit bugs in product Product A"īut I want users of "Group UsersA" should not edit the bug (that is fine) but must be able to post the comment.Bugzilla is an open-source tool used for issues and bugs tracking system. (Works fine ) When I use the above guide, it works perfectly except posting comments. In your particular setup, this is already covered by the EditA and EditB groups. If you want to restrict editbugs privileges in other products, you need to set up a group they are not a member of as xx/xx/xx/Canedit for the other products. For this, you need to give editbugs privileges to developers. ReadCreateA: Entry/Mandatory/Mandatory/- EditA: -/NA/NA/Canedit Similar for Product B. As i have ProductA, ProductB and groups Client, Developer. The following discussion was very helpful for me. Only Developer should able the create/edit the fields but Client should not able to edit the bug. How i can limits the users belongs to group B ? But there is no difference between the user's rights those either belongs to group A or B (both can create and edit bugs). Group A have full permissions (Create and Edit bug) but group B don't have any permission but only READONLY. Permission/restrictions on groups are also not working. I also want to customize some text fields/areas for for Bug Creator (who files the new bug) so that he/she can not edit his/her posted bug.Ĭan we customize these fields via making changes in code ? or by installing some plugins ? or any other way ? ![]() I want to customize some text fields/areas for that user, so that he/she can not edit that specific field. Each component have several reported bugs.Įvery bug has been assigned to a specific user. I have one product and several components of this product.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |