#Bugzilla skin how to
#Bugzilla skin code
#Bugzilla skin Offline

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.

#Bugzilla skin Offline

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 how to

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.

#Bugzilla skin code

HELL YES! – If bugs.I'm aware this isn't exactly a programming question, but it directly impacts our developers and the code we're assigned to write.

This release contains major improvements to search, support for SQLite, improved WebServices, and lots of other enhancements. All of today’s releases contain security fixes.”Ĥ.0.4: “All of today’s releases contain security fixes.Ĥ.0.3: “all of today’s releases contain security fixes. Quotation of fixes + improvements from: and subpagesĤ.2: “It has been a year since we released Bugzilla 4.0 in February of 2011, and this new major release comes with several new features and improvements. So why do we have to use Bugzilla 4.0.2 (Checked on ), when 4.2.1 is out Why do we recommend anyone the latest LibreOffice (from this or the last branch)? It is a) safer or/and b) better