In an effort to streamline communication, we're going to be formatting our ticket comments in such a way as to mirror that of a typicall scrum meeting. Basically it consists of putting the answers to the 3 questions into a comment along with other necessary information.

The main headings are Objective, Accomplishments, Problems, and Plan. An additional heading would be "Meeting Requested" or the like. With respect to filling in these comments, try not to make them short and sweet. They need to convey a broad amount of information about the ticket.

Please be sure to use the "preview" functionality before submitting your comment, as they are not editable after submission.

An example comment exists below:

---

Objective

I was going to finish the FooBar? function, the only thing missing is the zapping of the Bar in the fobb case.

Accomplishments

I got the fobb case resolved and tested. Actually I refactored some other cases too because there was too much duplication of code going on. See [15178]. I changed:

 if(giz()) {
   spaghetti();
   macaroni();
   cheez();
 } else if(fobb()) {
   spaghetti();
   tortellini();
   cheez();
 }

to

  spaghetti();
  foo.doTheRightThing();
  bar.addCheeze()

Problems

There is one case that dumps an exception as follows:

... stackdump of the root cause ...

the code that causes this is

  ...
  if(nix.foo() == nax)
    ...
  ...

and for some reason nix appears to be null. But I don't want to put just a null check in front because nix should never be null.

Plan

Tomorrow I'm going to try to trace back why nix ever comes up as null. I think it might have something to do with the Keexer class. Which we had designed based on the Keexer? ideas. because of ... So I'm going to ...

Meeting Requested

I need to meet with Mr X concerning this nix.foo....

---

Now we produce two reports, a daily and a 3-day report (spanning over weekends and holidays).

Daily Report

SELECT c.author AS __group__,
       ticket, time AS time, summary,
       newvalue as _description_
  FROM ticket_change c
    INNER JOIN (SELECT id, owner, summary FROM ticket) t ON(t.id = c.ticket)
  WHERE field='comment' AND c.author = t.owner
    AND time >= (strftime('%s','now') / 24 / 3600 - 2) * 24 * 3600
  ORDER BY author, ticket, time

Report of Previous 3 Days

SELECT c.author AS __group__,
       ticket, time AS time, summary,
       newvalue as _description_
  FROM ticket_change c
    INNER JOIN (SELECT id, owner, summary FROM ticket) t ON(t.id = c.ticket)
  WHERE field='comment' AND c.author = t.owner
    AND time >= (strftime('%s','now') / 24 / 3600 - 4) * 24 * 3600
  ORDER BY author, ticket, time

Which is working quite alright.

Wishlist:

• add total hours spent on task during last period
• add stories from scrum cycle which have no update
• order by child tasks