summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrédéric Buclin <LpSolit@gmail.com>2010-07-15 12:24:06 +0200
committerFrédéric Buclin <LpSolit@gmail.com>2010-07-15 12:24:06 +0200
commit14d8af1b61b19c623875d8f454ad1a45104c7e13 (patch)
treef387f8a7bcabaad631307733ba28a52a10488f9e
parent08c354cb29aa82eec4b9b9a0f4a947dd835b96d6 (diff)
downloadbugzilla-14d8af1b61b19c623875d8f454ad1a45104c7e13.tar.gz
bugzilla-14d8af1b61b19c623875d8f454ad1a45104c7e13.tar.xz
Bug 472452: Rephrase documentation about deleting custom fields
r=glob
-rw-r--r--docs/en/xml/administration.xml11
1 files changed, 7 insertions, 4 deletions
diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml
index 8d2ab64bd..ba356d4d1 100644
--- a/docs/en/xml/administration.xml
+++ b/docs/en/xml/administration.xml
@@ -2439,10 +2439,13 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
<title>Deleting Custom Fields</title>
<para>
- It is only possible to delete obsolete Custom Fields
- if the field has never been used in the database.
- To remove a field which already has content,
- mark it as obsolete.
+ Only custom fields which are marked as obsolete, and which never
+ have been used, can be deleted completely (else the integrity
+ of the bug history would be compromised). For custom fields marked
+ as obsolete, a "Delete" link will appear in the <quote>Action</quote>
+ column. If the custom field has been used in the past, the deletion
+ will be rejected. But marking the field as obsolete is sufficient
+ to hide it from the user interface entirely.
</para>
</section>
</section>