193242 - Add documention for customizing the Status, Resolution, Severity, Priority, Hardware and OS fields

Status: RESOLVED FIXED

(Bugzilla :: Documentation, defect, P3)

Description

[eric gorr]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130

In a conversation with Dave, he stated

for all of those except status and resolution, just edit the list in localconfig
and run checksetup.pl again

resolution you can do the same as long as you don't touch '', 'MOVED' or
'DUPLICATE', but you'll have to edit checksetup.pl itself for that one.

status is hard-coded all over the place.

you can change those, but it involves changing code.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Dave Miller [:justdave]]

confirming...

Comment 2

[Dave Miller [:justdave]]

Jake is leaving for a while (Reserve unit got called up), and we don't have a
new docs owner yet.  Anyone interested in helping out, please add
[e-mail] to your watch list in your email preferences in Bugzilla.

Comment 3

[Steven Penn]

I would think to most users this would be a critical bug.  The process is 
supported by the tool; not the tool drives the process.  I would guess that 
some [many?] potential users have looked at the tool, but discarded it since 
the ability to tailor it to their process was not evident.

Comment 4

[Tobias Sager]

From current documentation:
<snip>
2.2.1. localconfig

Once you run checksetup.pl with all the correct modules installed, it displays a
message about, and write out a file called, localconfig. This file contains the
default settings for a number of Bugzilla parameters.

Load this file in your editor. The only value you need to change is $db_pass,
the password for the user you will create for your database. Pick a strong
password (for simplicity, it should not contain single quote characters) and put
it here.

The other options in the localconfig file are documented by their accompanying
comments. If you have a slightly non-standard MySQL setup, you may wish to
change one or more of the other "$db_*" parameters.

You may also wish to change the names of the priorities, severities, operating
systems and platforms for your installation. However, you can always change
these after installation has finished; if you then re-run checksetup.pl, the
changes will get picked up.
</snip>

I propose to simply add:
<snip>
Please note that it currently is not possible to change status' names. If you
would like to change the names of resolution, make sure you do not change "",
"MOVED" or "DUPLICATE" as these are fixed values as well. All the other
resolutions can be edited in checksetup.pl (customise the enumeration called
"resolution").
</snip>

Comment 5

[Dave Miller [:justdave]]

This documentation is going to be different for <=2.18 and >=2.19.3 because we
now have a field editor and these items are all in tables instead of enums....

Comment 6

[Gabriel Hernandez]

Additional note of Warning.  Tried this procedure on our internal instance 
(version 2.18) and it worked, but noticed that permissions on certain 
directories had been reset to default after running the .pl script.  You may 
want to consider updating checksetup.pl to check (and consequently not modify) 
directory permissions if they do not match default unless admin runs the script 
with a switch;  something like:

./checksetup.pl -dirdef

Comment 7

[Frédéric Buclin]

The docs patch from bug 281876 already covers this. No need to update the docs on 2.18, first because it's pretty dangerous to customize things there, especially statuses and resolutions, and secondly because we will stop supporting 2.18 in a few weeks/months, so it's a bit late to learn how to customize this stuff on this branch (this bug was opened 3.5 years ago!).