Column View with Effort Summing in Days

Column View with Effort Summing in Days

[Malcolm Matalka]

I'm on 8.2.10 and want to upgrade to the latest version in ELPA for est+
views, but I noticed that summation with {:} in column view does not
give output in days.  I've poked around the code a bit and it doesn't
seem to me like a configuration change.

Is there any way to get effort estimates printed in days (where number
of days is based on org-effort-durations?

The motivation for this is I'm planning a large project where the summed
estimates are in days and 180 hours is more difficult to grasp than 22.5
days.

Thank you,
/Malcolm

Re: Column View with Effort Summing in Days

[Nicolas Goaziou]

Hello,

Malcolm Matalka <mmatalka@gmail.com> writes:

> I'm on 8.2.10 and want to upgrade to the latest version in ELPA for est+
> views, but I noticed that summation with {:} in column view does not
> give output in days.  I've poked around the code a bit and it doesn't
> seem to me like a configuration change.
>
> Is there any way to get effort estimates printed in days (where number
> of days is based on org-effort-durations?
>
> The motivation for this is I'm planning a large project where the summed
> estimates are in days and 180 hours is more difficult to grasp than 22.5
> days.

You can control the output with `org-time-clocksum-format' (which should
be named differently BTW). See also `org-time-clocksum-use-fractional'
and `org-time-clocksum-fractional-format'.

Regards,

-- 
Nicolas Goaziou

Re: Column View with Effort Summing in Days

[Malcolm Matalka]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Malcolm Matalka <mmatalka@gmail.com> writes:
>
>> I'm on 8.2.10 and want to upgrade to the latest version in ELPA for est+
>> views, but I noticed that summation with {:} in column view does not
>> give output in days.  I've poked around the code a bit and it doesn't
>> seem to me like a configuration change.
>>
>> Is there any way to get effort estimates printed in days (where number
>> of days is based on org-effort-durations?
>>
>> The motivation for this is I'm planning a large project where the summed
>> estimates are in days and 180 hours is more difficult to grasp than 22.5
>> days.
>
> You can control the output with `org-time-clocksum-format' (which should
> be named differently BTW). See also `org-time-clocksum-use-fractional'
> and `org-time-clocksum-fractional-format'.

From what I can tell, those apply to CLOCKSUM but in this case I'm using
{:} for effort.  Do they still apply there?  I can see that CLOCKSUM
already uses days in the format but I'm not seeing it on the output for
Effort sums.  Am I misunderstanding your response?


>
> Regards,

Re: Column View with Effort Summing in Days

[Nicolas Goaziou]

Hello,

Malcolm Matalka <mmatalka@gmail.com> writes:

> From what I can tell, those apply to CLOCKSUM but in this case I'm using
> {:} for effort.  Do they still apply there?

They should, IIRC, as long as at least one duration is expressed using
`org-effort-durations' units.

> I can see that CLOCKSUM already uses days in the format but I'm not
> seeing it on the output for Effort sums.

Could you show an ECM if you think it doesn't work as expected?

Regards,

-- 
Nicolas Goaziou                                                0x80A93738

Re: Column View with Effort Summing in Days

[Malcolm Matalka]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Malcolm Matalka <mmatalka@gmail.com> writes:
>
>> From what I can tell, those apply to CLOCKSUM but in this case I'm using
>> {:} for effort.  Do they still apply there?
>
> They should, IIRC, as long as at least one duration is expressed using
> `org-effort-durations' units.
>
>> I can see that CLOCKSUM already uses days in the format but I'm not
>> seeing it on the output for Effort sums.
>
> Could you show an ECM if you think it doesn't work as expected?

Ohhhhhhhhhkay, now I get what's going on.  It works if I have at least 1
effort estimate in days.  What does not work is if the sum of effort
estimates sums up to over a day, it stays as hours.  I don't know if
this behaviour is better or worse than my expected behaviour.  For my
usecase I do have some estimates that are over a day but the legacy
behaviour would automatically convert.

Here is an example:

* Test1
:PROPERTIES:
:COLUMNS: %50ITEM(Task) %10Effort(Effort){:}
:END:
** Foo
:PROPERTIES:
:Effort:   8:00
:END:
** Bar
:PROPERTIES:
:Effort:   8:00
:END:
** Baz
:PROPERTIES:
:Effort:   8:00
:END:

This sums to 24:00, if I change 1 of these to 1d I get 3d (which is what
I want).

Thank you!

>
> Regards,