Project Deferred or Greyed Automatically when Next Action is Deferred

I’ve noticed recently some projects are being deferred (greyed) automatically when the next action is being deferred. I rather have the projects remain active and not greyed because I have a perspective I use to review active projects. Any advice would be appreciated thanks.

This is by design. The projects are not deferred or inactive, it’s a way of showing you that there is no next action you can currently take to progress the project, either the next action is deferred as you’ve found, or assigned to a context/label which is on hold.

E.g. I have my waiting context on Hold, it means that I can ignore those projects when choosing next actions. At any time I can look at the “Waiting” context to see all of the actions I’m waiting for.

What if there were an attribute of the project, read-only, set by OmniFocus, and visible in the Inspector, that indicates the current status of a project? It could indicate a project status of deferred, inactive, or (as in this case) stalled.

The project is if I remember correctly considered to be blocked or unavailable in OF terms. Which are other words for there‘s nothing to be done here at the moment.

I don’t understand the purpose of an attribute visible in the inspector.

The greyed out project title clearly shows that there is no available action within the project, if the next action is “held” (Tag assigned to the next action is on hold or project on hold) there’s a Pause symbol in a circle next to it, otherwise there’s no next action and it’s stalled.

My thinking was that a metadata property would make it clear why a project was grayed out. Because it lacked a next action? Because it was paused?

Clearly, the OP found the current situation ambiguous.