Start a new topic

TODO items marked DONE but with CLOSED timestamp

I love the easy TODO/DONE swipe-switching in the TODO view of the app. The drawback is that in beorg when a TODO is converted to DONE, no `CLOSED: [timestamp]` is inserted, like it would be in Emacs.


4 people like this idea

I'm going to get those live on the website today :)

@Matthew: thanks a lot that was exactly what I was looking for. Somehow I missed it the info that customization is document within the app. Maybe a link to the library-org page in the manual would be useful. If it exists and didn't search properly shame on me

@Matthew: Thanks for considering the change! :) 

Take a look at https://beorg.app/manual/library-org/ which summarises the options available to configure beorg. You are probably looking for 

org-log-into-drawer, which by default is set to #f rather than a drawer name.

Christian - I missed your comment when you originally posted it. I've added some code to handle the per-item property LOGGING when set to nil so that it doesn't add any state transition notes.

1 person likes this
The logging appears directly in the notes not in the :LOGBOOK: drawer. Is there a setting to change that that I'm overlooking?

Is the configuration of this feature documented?


I do want the completion date to be logged for most one-off items, but not for recurring items like "water the plants" because that's just happening too often :)


The per-item properties work in Emacs, but not beorg:

 

SCHEDULED: <2019-09-05 Thu 14:00 +1w>
:PROPERTIES:
:LOGGING: nil
:END:

 

Thanks Kevin!

I can’t thank you enough @Matthew Kennard for this latest addition (repeated task state logging). It took me a while to get around to thanking you because I’ve been so engrossed in customizing my beorg workflow now that I practically live in your app. By far my favorite app. Keep up the good work!

No problem, thanks for confirming it is working.

Okay you're right. I can confirm it works. I expected somehow like a CLOSED:XXXX text, but your solution is like the original org behaviour and somehow I overlooked it. Sorry for the unnecessary trouble.

Make sure you are not overriding org-log-repeat in your init.org. It should be set to 'time for logging to occur.


As a test try the following:


+ In beorg tap the + to create a new item

+ Set Scheduled to today and repeat to every 1 weeks

+ Still on the New Item screen change the state from TODO to a DONE state

+ You should see added in the Notes section something similar to: State "DONE" from "TODO" [2019-05-23 Thu 10:46]


If the above doesn't check that the state you are setting the item to is in your "Done States" as defined on the Settings screen.


If the above does work please paste the contents of a sample item onto the forum with a repeat modifier for which changing to a done state isn't logging as it should.

Since yesterday I have the mentioned 2.14.1 version. I marked varoius recurring tasks as done, but unfortunately I don't see any additional logging of the state change. 

Then I am looking forward to get it. I am also in your testflight group and maybe it will be available as beta soon. :-)

beorg 2.14.1 will log state changes when recurring tasks are closed - this will probably be released this week, just waiting on approval from Apple. beorg doesn't yet have support for property drawers so won't include the LAST_REPEAT yet - but that will be coming in a future update.


1 person likes this

Just wanted to add that I also would like to have closing time stamps for recurring tasks. Without them it's not possible to see when the last occurences were.


Personally I prefer orgmode standard behaviour for those time stamps and probably a status for each keyword change would be nice as well.


image



Login or Signup to post a comment