Start a new topic

Next Actions agenda


   Great app, I'm loving it! I have configured a "Next Actions" agenda view in Emacs to show me just the next action for each project using the org-agenda-skip-function as described here [0]. I was wondering if it would be possible to duplicate the same functionality in Beorg? In other words, to customize the agenda as described in the org-mode documentation [1]. This would be helpful for anyone following David Allen's "Getting Things Done" paradigm.



Kind regards,

Bob Wilson

1 person likes this idea

I have used the same agenda skip function in Emacs before, but now find it much more elegant to use the "ORDERED" property on a project and to set org-agenda-dim-blocked-tasks to true (grey out the blocked tasks). This way I can easily mix sequential and parallel projects and only the next actions show up in the agenda.

Unfortunately, amazing as the app is, the ordered property is currently not supported in beorg. It would be great if that were the case!

I would like to look at making search, sort (and grouping) much more flexible to give you the kind of flexibility you would like. I'm currently working on subfolder support and better support for using beorg for note taking. Hopefully once that is complete and working well my next big beorg project will be to look at this.

That's great to read! 

Hey I'm wondering if the recent updates to search will now support this use case. Iminterested in using beorg for this as well.

I have the following saved search in beorg called "Task Board":


Breaking this down:

  • Group the results by state (the order of the states will match the order defined on the Settings tab)
  • Only show a headline which has one of the following states - NEXT, IN-PROGRESS or WAITING
  • Sort within the group alphabetically by file

In Emacs I then have a custom agenda command:

  (setq org-agenda-custom-commands
        '(("n" "Agenda + Task Board"
          ((agenda "")
           (todo "NEXT")
           (todo "IN-PROGRESS")
           (todo "WAITING")))))

2 people like this

can you clarify a bit how you use this in practice? For instance, say I have some tasks as part of a project:


* NEXT Cut Bread
* TODO Toast Bread
* TODO Apply Butter
* TODO Apply Jam
* TODO Eat Delicious Toast


So from the agenda I can mark "Cut Bread" as DONE. Then do you need to open the project org file and set the status of "Toast Bread" to "NEXT" manually? If your tasks are pretty granular that seems like a lot of bookkeeping. The benefit of the approach linked in the first post is that the agenda always stays up-to-date with your next task (assuming they're ordered within the project).

You are right in that beorg doesn't manually bump up the next task to NEXT. That however would only apply if the tasks were strictly serial - and there weren't any tasks which can happen in parallel. I personally set NEXT manually for some projects so that I know I'm ready to tackle that task - there may be multiple tasks set to NEXT and then I can choose which one to do.

Login or Signup to post a comment