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.
+1 for task state change logging, including for repeated tasks.
@Kevin good points about more general state change logging and repeated tasks.
I’m going to take a look at this relatively soon. I’m probably going to delegate this to a Scheme method and provide a sensible default implementation - then users with a more custom workflow can replace the Scheme implementation with their own as they see fit.
Awesome—looking forward to this. I think task completion logging, including repeated tasks, would be a huge help. Logging other state changes, e.g., TODO -> WAITING, is a much lower priority that can certainly be relegated to Scheme methods. Thank you so much for this project!
Also +1 on this logging. I basically just want to have a good story of “what kinda tasks did I complete on a given date”.
I’d even send tips for this.
I tried setting TODO keywords in settings to TODO and DONE(!) , but this was taken literally. Then tried setting org-todo-keywords in init.org. Didn’t work. Then also tried to put a line “#+TODO: TODO | DONE(!)” into inbox.org. Didn’t work either :/
Thanks @Matthew Kennard for adding the CLOSED timestamp line for DONE tasks in the latest update. Beorg is now so close to being an app that I live in. I still handle all task completion in org-mode since there’s no automated way to log state changes for repeating tasks, so I end up not using beorg all that often. The ability to log DONE for repeating tasks would be a total game changer.
I’d written the code for this when adding support for CLOSED timestamps and notes it just needed a little more testing. This should be available in the next update.
That’s so exciting to hear. Looking forward to the next release!
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.
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.
Then I am looking forward to get it. I am also in your testflight group and maybe it will be available as beta soon. :-)
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.
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.
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.
No problem, thanks for confirming it is working.
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!
Thanks Kevin!
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:
The logging appears directly in the notes not in the :LOGBOOK: drawer. Is there a setting to change that that I’m overlooking?
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.
@Matthew: Thanks for considering the change! :)
@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
I’m going to get those live on the website today :)
