ng to track the time an item is in queue,
and not the time the item is worked on.
>
> This is a different workflow than your current one - it uses the Org clocking
> feature, not just the TODO status feature.
>
> -k.
>
> On 2019-04-23 at 08:07 +0200, Malcolm Matalka wrote...
&
Ken Mankoff writes:
> Hi Malcom,
>
> On 2019-04-17 at 14:20 +0200, Malcolm Matalka wrote...
>> Is it possible in org-mode to track, and report, the duration of
>> certain state transitions in org-mode? In particular, I'm interested
>> in tracking how long it
Marcin Borkowski writes:
> On 2019-04-18, at 17:34, Malcolm Matalka wrote:
>
>> Marcin Borkowski writes:
>>
>>> On 2019-04-17, at 14:20, Malcolm Matalka wrote:
>>>
>>>> Hello,
>>>>
>>>> Is it possible in org-mode to
Marcin Borkowski writes:
> On 2019-04-17, at 14:20, Malcolm Matalka wrote:
>
>> Hello,
>>
>> Is it possible in org-mode to track, and report, the duration of certain
>> state transitions in org-mode? In particular, I'm interested in
>> tracking how
Hello,
Is it possible in org-mode to track, and report, the duration of certain
state transitions in org-mode? In particular, I'm interested in
tracking how long it takes me to go from a state that means I'm actively
working on an item to it being in a done state?
In my case, an item might go fr
Eric S Fraga writes:
> On Thursday, 15 Feb 2018 at 02:24, Malcolm Matalka wrote:
>> clocktable tries to be smart and convert hours to days, but in my
>> situation it'd actually be nicer if clocktable just kept everything in
>> hours. Is this possible?
>
> Check
clocktable tries to be smart and convert hours to days, but in my
situation it'd actually be nicer if clocktable just kept everything in
hours. Is this possible?
/Malcolm
Hello, has anyone had an opportunity to review this? Thank you.
Den 18 jan. 2017 9:33 em skrev "Malcolm Matalka" :
> Hey, this is my first elisp programming so I'm quite certain this is a
> big hack. I just stole elements from elsewhere in the file. I'm hoping
&g
Den 18 jan. 2017 22:19 skrev "Nick Dokos" :
Malcolm Matalka writes:
> Hey, this is my first elisp programming so I'm quite certain this is a
> big hack. I just stole elements from elsewhere in the file. I'm hoping
> this is good enough to get accepted then pe
Hey, this is my first elisp programming so I'm quite certain this is a
big hack. I just stole elements from elsewhere in the file. I'm hoping
this is good enough to get accepted then perhaps someone with more taste
would be able to refactor it to be a bit better.
Let me know if I need to change
Den 12 jan. 2017 15:10 skrev "Nicolas Goaziou" :
Hello,
Malcolm Matalka writes:
> When you use est+, what units are the ranges in?
"est+" expects numbers without units, e.g., "1-2".
Thanks again! Is supporting units something that is viewed as a bad idea
When you use est+, what units are the ranges in? For example, I did
1d-2d and then another which was 40:00 and got a very different result
than doing 5d instead of 40:00. I also tried with use 40h-40h and 5d-5d
and 40:00-40:00. Are ranges unit-less and I just have to be careful to
always use the
Nicolas Goaziou writes:
> Hello,
>
> Malcolm Matalka 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 u
Nicolas Goaziou writes:
> Hello,
>
> Malcolm Matalka 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
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 print
15 matches
Mail list logo
