diff --git a/src/main/resources/org/jenkinsci/plugins/parameterizedscheduler/ParameterizedTimerTrigger/global.jelly b/src/main/resources/org/jenkinsci/plugins/parameterizedscheduler/ParameterizedTimerTrigger/global.jelly
deleted file mode 100644
index 45fa385..0000000
--- a/src/main/resources/org/jenkinsci/plugins/parameterizedscheduler/ParameterizedTimerTrigger/global.jelly
+++ /dev/null
@@ -1,21 +0,0 @@
-<?jelly escape-by-default='true'?>
-<j:jelly xmlns:j="jelly:core" xmlns:st="jelly:stapler" xmlns:d="jelly:define" xmlns:l="/lib/layout" xmlns:t="/lib/hudson" xmlns:f="/lib/form">
-  <!--
-    This Jelly script is used to produce the global configuration option.
-
-    Jenkins uses a set of tag libraries to provide uniformity in forms.
-    To determine where this tag is defined, first check the namespace URI,
-    and then look under $JENKINS/views/. For example, <f:section> is defined
-    in $JENKINS/views/lib/form/section.jelly.
-
-    It's also often useful to just check other similar scripts to see what
-    tags they use. Views are always organized according to its owner class,
-    so it should be straightforward to find them.
-  -->
-  <f:section title="Hello World Builder">
-    <f:entry title="French" field="useFrench"
-      description="nothing to see here, move along. Check if we should say hello in French">
-      <f:checkbox />
-    </f:entry>
-  </f:section>
-</j:jelly>