+ Added sysconf stage modal view

1 files changed, 34 insertions, 0 deletions

diff --git a/app/view/sysconf/stage.modal.view.php b/app/view/sysconf/stage.modal.view.php
new file mode 100644
index 0000000..4eaab43
--- /dev/null
+++ b/app/view/sysconf/stage.modal.view.php
@@ -0,0 +1,34 @@
+<div id="stageModal" class="modal fade" tabindex="-1" role="dialog">
+    <div class="modal-dialog" role="document">
+        <div class="modal-content">
+            <div class="modal-header">
+
+                <button type="button" class="close" data-dismiss="modal">
+                    <span aria-hidden="true">&times;</span>
+                </button>
+
+                <h4 class="modal-title">Pad Stages</h4>
+
+            </div>
+
+            <div class="modal-body">
+                <p>The issue-tracking aspect of pads is divided up using pad stages.  A stage is
+                representative of the level of completion or high-level status of an issue.  For
+                example, a pad may have an initial stage named "To Do", an intermediate stage named
+                "In Progress", and another stage "In Review".  Stages form a sequence in practice.
+                When the appropriate amount of work has been done on an issue, it is advanced to the
+                next stage in the pipeline.  This allows other pad members and the issue's owner to
+                at a glance get an idea of the high-level progress of the issue.</p>
+
+                <p>Once an issue is closed, it is removed from this stage pipeline, but retained in
+                the pad itself for archival purposes and for generating reports.</p>
+            </div>
+
+            <div class="modal-footer">
+                <button type="button" class="btn btn-primary" data-dismiss="modal">
+                    Close
+                </button>
+            </div>
+        </div>
+    </div>
+</div>