Many features that users are asking for depend on customizing the templates used by Bugzilla. At this time we are using stock templates. This bug is intended to serve as a "meta bug" for all issues that rely on custom templates.
*** Bug 190594 has been marked as a duplicate of this bug. ***
I just wanted to add something to this bug so requesters understand what the holdup is. This *isn't* about a lack of templates / ideas / people (although some of that is also missing). This bug is about the process we have for maintaining our local patchset so we don't lose them on upgrades. we don't want to do lots of adhoc changes and then forget about them. Ideally we import stock bugzilla somewhere, branch it, apply our patches, etc. etc. This is going to happen. We just need to figure out how.
I might be able to assist with this. At my previous job I took their bugzilla 2 custom system and ported it over to 3 and added custom templates.
What's the status of this bug?
The custom templates (read: process of rolling out own customizations) has been discussed and agreed on so far. The essence is: - use a stock devel/bugzilla44 installation - copy https://github.com/freebsd/bugzilla/ over it - do administrative fine tuning That being said, changes to a clean-room installation of bugzilla should be kept at a minimum. Whereever possible, we shall use bugzilla's customization capabilities.