app/view/sysconf/issue.modal.view.php


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
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">&times;</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>