From fd415e6d1054795f8643e909061f7cd0cd5c5318 Mon Sep 17 00:00:00 2001 From: M <m@lfurio.us> Date: Sun, 29 Nov 2015 20:29:37 -0500 Subject: + Added sysconf issue modal view --- app/view/sysconf/issue.modal.view.php | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 app/view/sysconf/issue.modal.view.php (limited to 'app/view/sysconf/issue.modal.view.php') diff --git a/app/view/sysconf/issue.modal.view.php b/app/view/sysconf/issue.modal.view.php new file mode 100644 index 0000000..a77c1e3 --- /dev/null +++ b/app/view/sysconf/issue.modal.view.php @@ -0,0 +1,34 @@ +<div id="issueModal" 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">×</span> + </button> + + <h4 class="modal-title">Issues</h4> + + </div> + + <div class="modal-body"> + <p>Issues represent work. This work could be anything from a software project's bug + needing fixed or a new feature to implement to a record of needing to order more + celing panels for the new home office build. Work is done by someone, for someone, + and this is reflected in Scrott's internal data structures. Every issues has a + distinct owner (someone requesting work be done) and assignee (someone who needs to + do the work). If others are interested in the work or have valuable input on the + work, they may be included (cc'd) on the issue to receive updates on it or to be able + to post their own updates. Scrott tracks issues using pads which are representative + of a high-level project or some similar effort. So related issues are tracked + together.</p> + </div> + + <div class="modal-footer"> + <button type="button" class="btn btn-primary" data-dismiss="modal"> + Close + </button> + </div> + </div> + </div> +</div> -- cgit v1.2.3