Group project list by project status?

OmniFocus
1

I have a simple project list perspective that shows all my projects, whether active or on hold (paused/ waiting). I’d like to see the active projects first and then the ‘on hold’ projects but I can´t find a ´project status’ grouping option in the perspective (OF 3) . I suppose I could manually group them in two different folders but maybe there’s a more clever way of doing it?

2

I‘ve never thought about this, because I use two perspectives:

  • active projects
  • projects on hold

But you are right, there‘s no out of the box sorting for this. You could only use the first sorting option which should be called „Due Date and Flagged“ in English.

3

Thank you, @Logan. I have an active projects perspective, I suppose I can change my project list to an on hold project list.

I thought I was maybe missing something so your answer confirns that this is not the case.

Clearly not all fields in OF data model are searchable, which is understandable. I just wanted to recreate the GTD project list concept but it does not impact my workflow.

Thank for taking the time to answer

4

Indeed, there have been a number of requests for a couple of capabilities that would improve project based views:

  1. Be able to tag a project without automatically tagging the tasks underneath.
  2. Be able to show only certain projects tagged in this view (or, group by the tags; or only certain tags).

Your suggestion is a natural extension of what this flexible mechanism should involve.

I also note the project perspective view has a ton of extra vertical space wasting screen real estate (some of which shrinks when I click on things, some of which doesn’t). I assume this is ongoing challenges with switching to SwiftUI fairly early on.

5

Option 1 is even better. If you assign the project having a tag a new item. The item gets the project‘s tag as well. If the item had at least a tag before it won‘t get the project‘s tag.

Regarding option 2 I thing a #tag in the project‘s name is better.

Generally, I try to avoid tagging projects, because it easily gets messy. The logic is just too unnecessarily complex.