Bugzilla templates3/2/2023 ![]() ![]() See for background.įrom the shell prompt in the top level directory of the bugzilla installation: These are page appearance changes which need shell access to edit the template files on the web server. Name: cf_releasenotetext, Description: "Release Notes", Type: Large Text Box, Can be set on bug creation: No, Field only appears when: Product is set to Audacity.īug Status Workflow Groups Keywords Changes Made to the Templates.Name: cf_stepstoreproduce, Description: "Steps To Reproduce", Type: Large Text Box, Can be set on bug creation: Yes, Displayed in bugmail for new bugs: Yes, Field only appears when: Product is set to Audacity.'+' if passed, '-' if fails, '?' if hard to interpret results This bug reflects a design or implementation problem that hinders future changes to Audacityįixes for this bug will need test on Windows Mac and Linuxįor when a bug is perhaps NOT-A-BUG, allows different opinions to be voiced This bug is a regression compared to previous releases of Audacity Uncheck 'specifically requestable' and 'multiplicable'īug has security implications for users running Audacity Edit it's components and add a single component 'Wiki Manual'Īudacity:_Any_, Audacity manual:_Any_.Add a product 'Audacity Manual' with description 'The Audacity manual on '.Issues related to Labels and Label tracks Issues related to exporting/importing audio data ![]() Issues related to the Nyquist Lisp interpreter Issues related to the application core, library problems and similar things which are nothing to do with audio per se. Issues related to one or more built-in effects Issues relating to Audio playback and recording Issues relating to application User Interface Not the website, the forum, the bugtracker or anything outside of the core Audacity application.' set the description to 'Audacity itself.Random password which no-one needs to know, and doesn't need any system rights. Create a user " ", real name "Default Asignee for New Bugs", disable bugmail.These have to come after the field values have been set up Change Enhancement to 500 (we usually put Enh: at the start of the title too).CometReturns: 350 (for extremely rare bugs).RepeatableAll: 120 default (for bugs that are on all platforms).Severity (we will re-name this field and use it for bug type).the whole feature foo was disabled for release). Change 300 from INVALID to NOT-A-BUG ('INVALID' implies a report that had no use, 'NOT-A-BUG' doesn't).Add 'QUICKFIXED' at 250 (this is for bugs fixed before they every got out to users in a release).Change 'Windows' to 'Windows XP' at 200.Add a 'PX' value with sort key 50, so it goes at the top of the list.set quip_list_entry_control to Moderated at least (not open!).Make timetrackinggroup empty (nothing selected) to turn off time fields.defaultseverity (will be RepeatableAll) and defaultpriority (will be P4) are here, but we need to change the contents of the lists first.(usestatuswhiteboard should be already off).(usetargetmilestone should be already off). ![]() Turn letsubmitterchoosemilestone off (we aren't using milestones at the moment).Turn letsubmitterchoosepriority on (we are open source, so trusting contributors to know what they are doing makes sense).Set createemailregexp to blank, which means all accounts will have to be created by an administrator.The header is created by setting announcehtml to:Ĭlicking on the icon takes the user to a table like this one: announcehtml needs periodic changing, e.g to indicate when a new version of audacity is under development. Notice that the logo is served from our wiki. announcehtml This gives us the logo in top left, which is clickable and takes us to a table of bugs.Lots of things always need doing here, nothing is special to Audacity.For simplicity I have simply listed the end result for each form, although it will probably require multiple actions to get there (e.g. Most of the configuration of Bugzilla is done by logging in to the web interface as an administrative user and using the pages accessed from the Administration link in the footer. It assumes you have already set up and installed Bugzilla so you have a working vanilla installation. It should be updated when newer Bugzilla releases are deployed, although most of the work won't need to be re-done because the changes are stored in the database not in the installation files. This guide was written whilst customising bugzilla 3.4.1 because it was what I had handy. Bug Lists - for quick links to some bugzilla bug reports (and explanation of our priorities). ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |