I am using COLUMN VIEW to see a summary of worked and estimated hours. But I am getting some strange results. In one big org file I clocked all my work in different atomic tasks (The file is mixed with English and Portuguese ). For example: * Apontamento de Horas Gerais ** Atendimentos / Serviços *** Estudo Técnico (externo) *** Suporte Técnico :CLOCK: CLOCK: [2008-11-25 Tue 14:30]--[2008-11-25 Tue 19:30] => 5:00 CLOCK: [2008-11-24 Mon 13:58]--[2008-11-24 Mon 14:39] => 0:41 CLOCK: [2008-11-24 Mon 13:11]--[2008-11-24 Mon 13:48] => 0:37 CLOCK: [2008-11-24 Mon 07:00]--[2008-11-24 Mon 07:30] => 0:30 :END: **** My Customer ***** Motor and valves problem ( go down ) :CLOCK: CLOCK: [2008-12-01 Mon 13:00]--[2008-12-01 Mon 15:24] => 2:23 CLOCK: [2008-11-26 Wed 15:28]--[2008-11-26 Wed 15:40] => 0:12 :END: ***** 09.00698 - Technical Support CLOCK: [2009-02-02 Mon 15:15]--[2009-02-02 Mon 16:56] => 1:41 Then I decided to start with PROPERTIES for item "09.00698 - Technical Support", and my file became: * Apontamento de Horas Gerais :PROPERTIES: :COLUMNS: %50ITEM %10CLOCKSUM(Clocked) %5Effort(Estimate){:} %5HourSold(Sold){:} :ID: apontamento_horas :END: ** Atendimentos / Serviços *** Estudo Técnico (externo) *** Suporte Técnico :CLOCK: CLOCK: [2008-11-25 Tue 14:30]--[2008-11-25 Tue 19:30] => 5:00 CLOCK: [2008-11-24 Mon 13:58]--[2008-11-24 Mon 14:39] => 0:41 CLOCK: [2008-11-24 Mon 13:11]--[2008-11-24 Mon 13:48] => 0:37 CLOCK: [2008-11-24 Mon 07:00]--[2008-11-24 Mon 07:30] => 0:30 :END: **** My Customer ***** Motor and valves problem ( go down ) :CLOCK: CLOCK: [2008-12-01 Mon 13:00]--[2008-12-01 Mon 15:24] => 2:23 CLOCK: [2008-11-26 Wed 15:28]--[2008-11-26 Wed 15:40] => 0:12 :END: ***** 09.00698 - Technical Support :PROPERTIES: :Effort: 20:00 :HourSold: 21:00 :END: CLOCK: [2009-02-02 Mon 15:15]--[2009-02-02 Mon 16:56] => 1:41 Then I generate a table using the code: #+BEGIN: columnview :hlines 2 :vlines t :id "apontamento_horas" :skip-empty-rows t #+END: The code works fine and my table is ok, but I have some errors when: 1) If I want my CLOCKED column to be the last one and Estimate at first column, all clocked values are filled in the first column anyway, although it is Estimate. So the solution for this problem was to consider the CLOCKED always as the first column. 2) If I consider both Effort and HourSold Properties with the value of 20:00 under item "09.00698 - Technical Support", I get an empty column under Sold in the summary table. So the solution for this problem was to consider the Effort 20:00 and Sold 21:00 then I get the correct summary. I am using org-mode 6.12b and emacs 22.2.1. Is it a real problem or I am doing anything wrong? Regards, Flávio.
[-- Attachment #1: Type: text/plain, Size: 2452 bytes --] -- Mar 3/2/09, Flávio <flaviostz@gmail.com> ha scritto: [snip] > Then I decided to start with PROPERTIES for item > > * Apontamento de Horas Gerais > :PROPERTIES: > :COLUMNS: %50ITEM %10CLOCKSUM(Clocked) > %5Effort(Estimate){:} > %5HourSold(Sold){:} > :ID: apontamento_horas > :END: > ** Atendimentos / Serviços > *** Estudo Técnico (externo) > > *** Suporte Técnico > :CLOCK: > CLOCK: [2008-11-25 Tue 14:30]--[2008-11-25 Tue 19:30] > => 5:00 > CLOCK: [2008-11-24 Mon 13:58]--[2008-11-24 Mon 14:39] > => 0:41 > CLOCK: [2008-11-24 Mon 13:11]--[2008-11-24 Mon 13:48] > => 0:37 > CLOCK: [2008-11-24 Mon 07:00]--[2008-11-24 Mon 07:30] > => 0:30 > :END: > **** My Customer > ***** Motor and valves problem ( go down ) > :CLOCK: > CLOCK: [2008-12-01 Mon 13:00]--[2008-12-01 Mon 15:24] > => 2:23 > CLOCK: [2008-11-26 Wed 15:28]--[2008-11-26 Wed 15:40] > => 0:12 > :END: > ***** 09.00698 - Technical Support > :PROPERTIES: > :Effort: 20:00 > :HourSold: 21:00 > :END: > CLOCK: [2009-02-02 Mon 15:15]--[2009-02-02 Mon 16:56] > => 1:41 > > Then I generate a table using the code: > > #+BEGIN: columnview :hlines 2 :vlines t :id > "apontamento_horas" > :skip-empty-rows t > > #+END: > > The code works fine and my table is ok, but I have some > errors when: > > 1) If I want my CLOCKED column to be the last one and > Estimate at first column, > all clocked values are filled in the first column anyway, > although it is > Estimate. So the solution for this problem was to consider > the CLOCKED always > as the first column. > > 2) If I consider both Effort and HourSold Properties with > the value of 20:00 > under item "09.00698 - Technical Support", I get > an empty column under Sold in > the summary table. So the solution for this problem was to > consider the Effort > 20:00 and Sold 21:00 then I get the correct summary. > > I am using org-mode 6.12b and emacs 22.2.1. Is it a real > problem or I am doing > anything wrong? Org 6.21b Emacs 22.3 WinXP I confirm this bug for the column view export: the column view is displayed correctly, also if the order of colums is changed, but the table, both if generated with C-c C-x i and with C-c C-c on the #+BEGIN columnviev line, is not correct. Please see also the image attached. cheers, Giovanni [-- Attachment #2: exp-port-col-table.png --] [-- Type: image/png, Size: 29083 bytes --] [-- Attachment #3: Type: text/plain, Size: 204 bytes --] _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
On Feb 3, 2009, at 11:50 AM, Flávio wrote: > I am using COLUMN VIEW to see a summary of worked and estimated hours. > But I am > getting some strange results. > > In one big org file I clocked all my work in different atomic tasks > (The file is mixed with English and Portuguese ). > For example: > > * Apontamento de Horas Gerais > ** Atendimentos / Serviços > *** Estudo Técnico (externo) > *** Suporte Técnico > :CLOCK: > CLOCK: [2008-11-25 Tue 14:30]--[2008-11-25 Tue 19:30] => 5:00 > CLOCK: [2008-11-24 Mon 13:58]--[2008-11-24 Mon 14:39] => 0:41 > CLOCK: [2008-11-24 Mon 13:11]--[2008-11-24 Mon 13:48] => 0:37 > CLOCK: [2008-11-24 Mon 07:00]--[2008-11-24 Mon 07:30] => 0:30 > :END: > **** My Customer > ***** Motor and valves problem ( go down ) > :CLOCK: > CLOCK: [2008-12-01 Mon 13:00]--[2008-12-01 Mon 15:24] => 2:23 > CLOCK: [2008-11-26 Wed 15:28]--[2008-11-26 Wed 15:40] => 0:12 > :END: > ***** 09.00698 - Technical Support > CLOCK: [2009-02-02 Mon 15:15]--[2009-02-02 Mon 16:56] => 1:41 > > Then I decided to start with PROPERTIES for item "09.00698 - > Technical Support", > and my file became: > > * Apontamento de Horas Gerais > :PROPERTIES: > :COLUMNS: %50ITEM %10CLOCKSUM(Clocked) %5Effort(Estimate){:} > %5HourSold(Sold){:} > :ID: apontamento_horas > :END: > ** Atendimentos / Serviços > *** Estudo Técnico (externo) > > *** Suporte Técnico > :CLOCK: > CLOCK: [2008-11-25 Tue 14:30]--[2008-11-25 Tue 19:30] => 5:00 > CLOCK: [2008-11-24 Mon 13:58]--[2008-11-24 Mon 14:39] => 0:41 > CLOCK: [2008-11-24 Mon 13:11]--[2008-11-24 Mon 13:48] => 0:37 > CLOCK: [2008-11-24 Mon 07:00]--[2008-11-24 Mon 07:30] => 0:30 > :END: > **** My Customer > ***** Motor and valves problem ( go down ) > :CLOCK: > CLOCK: [2008-12-01 Mon 13:00]--[2008-12-01 Mon 15:24] => 2:23 > CLOCK: [2008-11-26 Wed 15:28]--[2008-11-26 Wed 15:40] => 0:12 > :END: > ***** 09.00698 - Technical Support > :PROPERTIES: > :Effort: 20:00 > :HourSold: 21:00 > :END: > CLOCK: [2009-02-02 Mon 15:15]--[2009-02-02 Mon 16:56] => 1:41 > > Then I generate a table using the code: > > #+BEGIN: columnview :hlines 2 :vlines t :id "apontamento_horas" > :skip-empty-rows t > > #+END: > > The code works fine and my table is ok, but I have some errors when: > > 1) If I want my CLOCKED column to be the last one and Estimate at > first column, > all clocked values are filled in the first column anyway, although > it is > Estimate. So the solution for this problem was to consider the > CLOCKED always > as the first column. I don't seem to be able to reproduce this behavior. > > > 2) If I consider both Effort and HourSold Properties with the value > of 20:00 > under item "09.00698 - Technical Support", I get an empty column > under Sold in > the summary table. So the solution for this problem was to consider > the Effort > 20:00 and Sold 21:00 then I get the correct summary. Uhhh, very bad bug indeed. Fixed, thanks for finding that one! - Carsten