Time tracking

Strict time tracking is practiced on this project, since it has financial implications.
You must log work time daily, otherwise people forget and the picture becomes distorted.

And that means you, !

Logging time

go to the issue you want to log time for (or select it in the Issue Navigator)
select More Actions> Log Work (or Actions> Log Work in the Issue Navigator)
- better yet: use the keyboard shortcuts: ". lo Enter" (press "?" to see the keyboard shortcuts help)
enter "Time Spent" (in hours)
adjust "Date Started" if you're logging post-factum. Only the date must be correct, we don't care about the time
enter "Work Description". This should be very brief (eg "wrote first version of conf page")
- Anything that you want your peers to see (eg problem/warning) should be put in Issue Comment, since your peers don't read work logs (only your TL/PM does), and people don't get email notification on Work Logs (only on Issue Comments)
- Any substantive knowledge should be put in Confluence, and only referenced in the Issue
You have to enter a specific issue before seeing More Actions
OR at the issue navigator: go down/up with "j"/"k" then press "." and type "log"
You cannot log work against a Closed issue, so we shouldn't close unnecessarily (see below)

TimeSheet dashboard portlet

The TimeSheet dashboard portlet is the fastest way to see how much time you've logged this week.

Use this for a daily or weekly review in order to complete the number of hours (but log daily!).
You can configure the number of weeks.

To use it:

Select "Dashboard with TimeSheet and ActivityStream", which includes it
or create your own Dashboard (copying this one or System), then Add the portlet

What You Did Recently

I know I spent 9h in the office today, but I can barely remember half of it. So I use the following to find what I did today:

Jira Updated Issues
- unfortunately Jira cannot find all issues you updated recently.
  - updated=currentLogin() means "updated after my last login" and
  - assignee=currentUser() means "I'm responsible" (but I often work on other issues as well)
- TODO: after we install [HP-Palm Jira Plugins#Search], we'll have search for updatedBy
Jira Activity Stream
Confluence Profile> Activity
TODO: is there a way to see directly Activity?
Confluence Recently Viewed
SVN commits: TODO Mitac
emails sent or read today
Sorry can't help here

Earned Value Analysis

Simply put, EVA tells you how much you're behind schedule, and over budget, at any given point in time.
(Or ahead and saving money, but that never happens ).
The input to EVA are the plan estimates on one hand, and the actuals from time tracking, on the other.

TODO: refer to Earned Value Analysis as per offer
TODO: describe how we'll do monthly timesheet analysis with Pivot Report

Other Hints

Don't Close Unnecessarily

When you're done with something, do Resolve. There's no need to do Close to say that it's done.
You cannot lot work against a Closed issue, but we often need to add a forgotten log...
Only testers should Close. They hunt for Bugs (or Bug Subtasks) that are Resolved, test them, then Close them.

Use Correct Issue Types

Bugs are preferably posted as Bug Subtask under the corresponding feature task
Post a Bug / Bug Subtask only if the issue requires verification by a tester
Otherwise post Task, Subtask, Enhancement, whatever

Quick Search

A fast (but limited) way to look for issues is the Quick Search in the top right corner

my : all assigned to me
my unresolved : unresolved assigned to me
proton : all in project PROTON
my proton : in PROTON assigned to me
rs unresolved nuxeo : in project RS that are unresolved and mention "nuxeo" (RS is a project, "nuxeo" is not so is taken as FTS)

Posting Tasks

Normally TLs post tasks for people in their team.

You can post a task for yourself, as soon as you've discussed it with your TL and (s)he has agreed

Task conventions

all Jira tasks must have fixVersion and Component
- to find tasks that miss these, use this JQL query
  
  or this direct link
do not use multiple components. Select the one component that's most relevant. Else Time Spent statistics are screwed up.
tasks must be described in detail: as a detailed sequence of steps and description of the deliverable
tasks must not include substantial knowledge
- you should not expect a Closed task to be viewed by anyone
  (and a Resolved task is usually viewed only by QA)
- if you find yourself writing such knowledge, move it to a Confluence page and link it (use issue.Confluence custom field)
- if you have no time (like I often don't), at least create the page, and put a TODO linking back to the task.
bugs are preferably posted as Bug Subtask of the task implementing the feature

RS Jira Conventions