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
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
|
<head>
<title>Taglog tutorial - More about Projects</title>
<meta name="keywords" content="time management log tutorial">
<link rel=prev href="tutorial3.html" title="Tutorial - Preferences">
<link rel=up href="tutorial.html" title="Tutorial - Contents">
<link rel=next href="tutorial_with_others.html" title="Tutorial - working with others">
</head>
<body lang="en">
<h1>Taglog tutorial - More about Projects</h1>
<a href="http://johnlines.github.io/taglog/">Taglog</a> uses the term Project
to mean a label by which you wish to measure chunks of time.
<p>
In conventional usage a project has a beginning, a middle, and an end - but in Taglog there may also
be 'projects' which are ongoing. For example your company may want to account for time spent on
Safety activities seperately from work which is directly charged to particular customers.
<h2>Attributes of a project</h2>
<h3>Start and End Dates</h3>
By default when you <a href="#add">add a project</a> the start date is set to the current date
and the end date is not specified.
<p>
If you are working beyond the end date of the project then it is 'Closed' - which means that it
does not show up in the Project selector in the central menu bar for booking time to it.
It will still show up when picking entries by project in the File/Open... selector.
<h3>Booking Code</h3>
It may be that your projects have useful titles, such as 'New Computer Suite', but that you are
supposed to book to, for example 'P0152'. You can use the Booking Code field to record the names
your time booking system wants you to use for projects, and use a more meaningful name for your
own use.
<p>
It could also be that your administrative processes generate the official booking code some time
after you are expected to start work on the project. As long as you have a booking code by the
time you generate the Time Bookings Report taglog will work quite happily on just a title.
<h3>Breaks</h3>
Projects which are labeled as 'Breaks' are ones which are not working time. If you have, for example,
a lunch break which is not part of your working hours you could create a project called Breaks, and
'book' your lunch times to this project.
<p>
Breaks projects are counted seperately in the reports.
<h3>Overheads</h3>
You may have activities which can not be associated directly with an
individual chargeable project, but which should be spread in an
equitable manner across your other projects - for example filling in
your timesheets.
<p>
You can create one, or more, projects which are flagged as Overheads.
<h3>Active Projects</h3>
If you have a large number of projects which are Open (that is, the
current date is between their Start and End dates) then you may find
that they become difficult to manage. By flagging the ones you are
actively working on as Active they are moved to the top of the
Project selection list.
<p>
Projects which are marked as Active also always appear in the
Project Times display invoked through Projects/View.
<h3>Immutable Projects</h3>
Projects which are flagged as Immutable are (like Breaks projects) not eligible
to have Overheads time spread into them.
You might wish to use the Immutable flag for projects such as Bank Holidays, Leave,
or Sick Leave which should not be 'bulked out' with your administrative overheads.
<h2>Working with Projects</h2>
<h3><a name="add">Adding a Project</a></h3>
This is done through the Projects/Add menu item.
<h3>Editing a Project</h3>
This is done through the Projects/Edit menu item. You are presented with a scrollable
list of all the projects, and can use this to, for example change the Active flag on
a project - if you start actively working on it - or possibly if your involvement with
it is largely over. This is also where you set the end date of a project - usually to
todays date, to indicate that it is Closed, and hence no longer available for new
time bookings.
<p>
Note that you might have Actions which are associated with a project - and if you
close the project before you have finished all the actions (there is no check for
this yet) then you will still accumulate time booked to those actions as booked to
that project.
<h3>Deleting a Project</h3>
Projects can be deleted through the Projects/Edit menu entry. There is a 'Delete' checkbox
at the end of each project line. Select the Delete checkbox for each project you
wish to delete and click OK.
<p>
You may want to keep projects around for a while after they are closed so that they
still appear in the dropdown lists for the File/Open... selector.
<h3>Importing projects from a central server</h3>
It is also possible to set up a central server from which you can
import information on the available projects.
This is covered in the next section of the tutorial and is what the Projects/Update
menu item does.
<hr>
<a href=tutorial_with_others.html>Next</a>
<a href=tutorial3.html>Previous</a>
<a href=tutorial.html>Contents</a>
<address>
Author: <a href="https://paladyn.org/john/">John Lines</a>
<a href="mailto:john+taglog@paladyn.org">john+taglog@paladyn.org</a>
</address>
</body>
|
