Open Infrastructure

h1. How to use ctt

h2. General Ticket handling

* Tickets which are not in progress for the moment needs to be set as unassigned & seen

* New Tickets, should be unassigned & new

** these tickets need to be watched and changed in 1 day

h2. Introduction

* Installation of "ctt":https://code.ungleich.ch/ungleich-public/ctt.git (or compatible) (*[[for windows user]])

** clone the repository to a location you whish

<pre>

git clone https://code.ungleich.ch/ungleich-public/ctt.git ~/Work/bin/ctt

</pre>

** Edit your PATH environment variable

*** e.g. open your ~/.bashrc and append

<pre>

export PATH=$PATH:~/Work/bin/ctt/bin

</pre>

*** source your ~/.bashrc

<pre>

source ~/.bashrc

</pre>

** if you run "ctt" now you should see the usage of it

* *Send Dominique your ssh key, otherwise the next steps won't work*

* Clone the dot-ctt repository from git@code.ungleich.ch:ungleich/dot-ctt.git

<pre>

git clone git@code.ungleich.ch:ungleich/dot-ctt.git ~/.ctt

</pre>

* Track your time to "$customer-$yourname" (ctt track $customer-$yourname <ENTER>) for instance

** ungleich-$YOURNAME

** customer1-$YOURNAME

** customer2-$YOURNAME

* When you finished working, press <ENTER> once again then give a comment what you worked on (See details below)

* All times need to be pushed every friday

<pre>

cd ~/.ctt

git pull

git add ./*

git commit -m "added times"

git push

</pre>

* If working for a customer of a customer, include the customer/project name:

** IDENTIFIER; normal text

* When working on a *fixed budget* project for a customer, book the hours to ungleich

* If you are working at/for ungleich, your ctt entries will be reviewed, and logs not meeting the following criteria can/will be rejected.

** Time tracking *should not exceed 180 minutes* for one session of work

*** Write a good and concise description of the work done per entry.

*** Show the transparent progress of your task in the description.

*** If working on the same task for a long period of time, break it down in session description: avoid giving the same, repeated description for many entries happened over extensive hours. 

h3. Deleting tracked time entry

<pre>

rm -r ~/.ctt/$customer-$yourname/YYYY-MM-DD-HHmm

</pre>

Where YYYY-MM-DD-HHmm is the start time of your tracked entry.

e.g.

<pre>

rm -r ~/.ctt/ungleich-intern-user/2015-08-26-2030

</pre>

h3. Change the comment

The comment is stored in the following file:

<pre>

~/.ctt/$customer-$yourname/YYYY-MM-DD-HHmm/comment

</pre>

Just open this file with a text editor (e.g. vim, nano, Notepad++ etc. (NOT WORD)) and change it's content

h2. Times & Dates

* Enter times until friday every week (everybody)

* Verify time entries until sunday evening (Nico)

* Transfer times to customer systems until monday midday (David)

h2. Some time-entry examples

* You work for a Ticket of Customer

<pre>

ctt track customer-$YOURNAME

Comment = Customer; #TICKETNUMBER; Comment

</pre>

* You work internal hours

<pre>

ctt track ungleich-$YOURNAME

comment = Ungleich; (#TICKETNUMBER); Comment

</pre>

* You work on fix price Project of Customer

<pre>

ctt track ungleich-customer-$YOURNAME

comment = Customer; (#TICKETNUMBER); Comment

</pre>

* You worked on a project but forgot to track:

<pre>

ctt track ungleich-intern-$YOURNAME --sd YYYY-MM-DD-HHMM --ed YYYY-MM-DD-HHMM

comment = COMMENT

</pre>

You can leave the --ed part if you still working on it now

h2 Reporting your time

<pre>

cd .ctt

ctt report *${YOURNAME}

</pre>