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
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
<div id="padModal" 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">Pads</h4>
</div>
<div class="modal-body">
<p>Use pads to track tasks, issues, bugs, client tickets, etc. Within Scrott, these
are collectively referred to as 'issues'. Use a pad to track your progress on a
project's completion, to manage user issues for a help-desk, to keep a shopping list,
bucket list, lists to track your progress on a television series (or series you'd
like to start), or books to read, or anything inbetween.</p>
<p>In addition to issue tracking, pads enable users to communicate with one another.
Each pad consists of a lightweight message board (forum) and users can also post
messages directly to issues if they are relevant. With email integration, even
non-scrott users may be clued in to the progress of their open issues. Pads even
allow for message threads to be converted (elevated) to a new open issue if need be.
(for example: Imagine you started a thread to discuss a potential new website design.
Once your team had arrived at something the majority liked, the thread can be elevated
to a new issue (preserving all messaging history), assigned to one of the team
members, and tracked just like all of your other issues.)</p>
<p>If you would like to allow the public to open issues in your pad (ie: if your pad
is allowing bug reports/feature requests from users of your project or if your pad
is the issue tracker for a help-desk), you can enable an issue portal for your pad.
A portal is a page accessible to the public where anonymous internet users (with a
verified email address) may submit new issues to your pad. Their email address
becomes the issue owner so the requester is still able to receive updates on the
issue as well as respond with their own messages.</p>
<p>Pads can be used by a single user or many; and pads can be owned by a user or a
user group</p>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" data-dismiss="modal">
Close
</button>
</div>
</div>
</div>
</div>
|
