If you are installing a new Bugzilla, the latest stable release series (and so the one you should choose unless you have a good reason for doing otherwise) is the 5.0 series.
BUGZILLA SKIN HOW TO
That document also explains how to upgrade Bugzilla to a new version, move a Bugzilla installation between machines, and migrate from other bug-tracking systems. Instructions on how to do this are in the Installation and Maintenance Guide. This is true of both stable and development versions.
BUGZILLA SKIN CODE
I'm exploring options for using Trac here if you want to follow along.By far best way to get, maintain and upgrade Bugzilla is as a checkout from the appropriate branch of our source code control system.
I'm certain we're not the first production facility to run into problems like this, I'm looking for recommendations to help solve both our scalability as well as-ease-of-use problem.Īnother thought that occurs to me is a GAS script to push our current Google forms based bug reports into Trac or Bugzilla.Įdit: The decision between Bugzilla/Trac seems to have been made for us. TaskCompiler, found on the Bugzilla wiki site seemed like a candidate because it talks to both Bugzilla & Trac, but their sales page is offline and the site hasn't been updated since 2012 and I'm unsure as to their viability. Obviously I can figure this out but don't want to go down that path if it's not going to solve our basic problem which is non-technical people reporting bugs.
BUGZILLA SKIN INSTALL
I've found the winners of the " Make Bugzilla Pretty" contest, but coming from a pure software house where we just used straight Bugzilla out of the box, I'm unclear on how to configure and install these skins. Standard bug tracking features developers and management can use.Customizable for our software packages (like drop downs for each).Simplified bug reporting, a Wizard like approach seems to work well.Ideally we'd have a Windows >= XP web or desktop client that would provide: We're only a few weeks into this system and it's already showing it fragility and lack of scalability. We're currently manually cutting & pasting their bug/feature requests from the Google form spreadsheet into Trac, and manually tracking the bugs/feature requests on a white board with magnetic bug cards. However, they seem to like the simple Google form and the wizard-like steps to file a bug or request a feature. The company has tried using Bugzilla before my arrival with little success, the factory folks were apparently intimidated by it and wouldn't use it. We've implemented a very simple Google form based bug reporting page, but we're already running into problems of scale (approx 40:1 them:us and lots of old-old buggy software that we didn't write). Our work environment is a couple of developers creating (20-30%) and maintaining (lion's share) legacy software for factory production floor and test workers to use to calibrate or test the equipment the company sells. If there's another SO-like forum where this could be better posted, please let me know and I'll take the question down from here & post it there. I'm aware this isn't exactly a programming question, but it directly impacts our developers and the code we're assigned to write.
0 kommentar(er)
