Removes obsolete comment configuration from docs
Its-Jura does not use anymore the gerrit.config based commentOnXXX
configuration options and instead rely on the generic its-base
rule-based actions. Leaving obsolete traces of the legacy config in
the its-jira plugin config is quite misleading and it is better to
be removed.
Change-Id: Ia9b26f8904f0e740672f0e250e03ed0ba773e650
diff --git a/src/main/resources/Documentation/config.md b/src/main/resources/Documentation/config.md
index c11aec4..50a0cad 100644
--- a/src/main/resources/Documentation/config.md
+++ b/src/main/resources/Documentation/config.md
@@ -101,45 +101,6 @@
Jira credentials and connectivity details are asked and verified during the Gerrit init.
-Comment configuration
----------------------
-
-It is possible to choose which kind of Gerrit event will trigger the plugin to comment on
-the Jira issue by adding the following in your `gerrit.config` file under the `[its-jira]` section:
-
-commentOnChangeAbandoned
-: If true, abandoning a change adds a comment to the issue.
-
-commentOnChangeCreated
-: If true, creating a change adds a comment to the issue.
-
-commentOnChangeMerged
-: If true, merging a change adds a comment to the issue.
-
-commentOnChangeRestored
-: If true, restoring an abandoned change adds a comment to the issue.
-
-commentOnCommentAdded
-: If true, adding a comment or reviewing a change adds a comment to the issue.
-
-commentOnFirstLinkedPatchSetCreated
-: If true, creating a patch set for a change adds a comment to the issue if
- the issue has not been mentioned in previous patch sets of the same change.
-
-commentOnPatchSetCreated
-: If true, creating a patch set for a change adds a comment to the issue.
-
-commentOnRefUpdatedGitWeb
-: If true, updating a ref adds a comment to the issue.
-
-By default all parameters are set to true.
-
-Example:
-
- [its-jira]
- commentOnCommentAdded=false
- commentOnRefUpdatedGitWeb=false
-
Gerrit init integration
-----------------------