From: Malcolm Matalka <mmatalka@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Column View with Effort Summing in Days
Date: Thu, 12 Jan 2017 13:46:18 +0000 [thread overview]
Message-ID: <86wpe0bdcl.fsf@gmail.com> (raw)
In-Reply-To: <87vatkbece.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 12 Jan 2017 14:24:49 +0100")
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,
prev parent reply other threads:[~2017-01-12 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 11:50 Column View with Effort Summing in Days Malcolm Matalka
2017-01-12 12:58 ` Nicolas Goaziou
2017-01-12 13:12 ` Malcolm Matalka
2017-01-12 13:24 ` Nicolas Goaziou
2017-01-12 13:46 ` Malcolm Matalka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wpe0bdcl.fsf@gmail.com \
--to=mmatalka@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).