In OmniFocus for macOS 4.5 (v180.1.7) and OmniFocus for iOS 4.5 Pro (v180.1.2), there is a discrepancy in behavior when an entry item is marked complete within the QuickEntry editor or not.
The scenario is as follows: A project exists with a given tag associated with the project. Create an entry using QuickEntry and associate the entry with the project. Do not set any tags within QuickEntry.
The observation: If this entry is marked complete within QuickEntry, upon viewing the Completed entries’ perspective, the entry will only reference the project, it will not also include the associated tag from the project. However, if you were to not mark the entry as complete within QuickEntry, then locate the entry within the project and mark it complete, viewing the entry within the Completed entries’ perspective will properly attribute both the project and associated tag from the project.
The problem arises when a user has a custom perspective which filters on tags, the perspective may exclude certain entries from reporting (as they would only be visible within Untagged). My supposition is some preprocessing of an entry within a project is performed to assign tags, whereas this does not occur within QuickEntry when already marked complete. In any event, I did not expect this behavior. Is this the expected behavior or a bug?
Thanks for confirming the behavior. It would be great if someone from OmniGroup could confirm whether this behavior is expected or an issue. As a user it feels like an issue.
Everyone has a direct line to our support team, but these forums aren’t it! I happen to be catching up on these forums more than usual this week because I’m on holiday, but the best way to make sure something reaches our team is to send email to omnifocus@omnigroup.com. Unlike forum posts, email messages are tracked and assigned ticket numbers, because we know they’re addressed to us. We try to reply to each email message within one business day.
But I do happen to be here right now, and I’m happy to answer your question: That doesn’t sound like behavior I would expect either!
Thank you for your response, and for clarifying the preferred support route, I will note that in the future. Also, I’m glad to hear the behavior does not sound as if it should be expected!
I originally reported this issue via that email address on 5/1/2024, but the issue specifically mentioned macOS at the time. I later confirmed the behavior (and reported via email) the same behavior on iOS. With the release of OmniFocus 4.4 mentioning changes to Quick Entry, I was following up to see if the behavior was still present in the newer releases, and whether others were also experiencing it (or if my utilization was off-kilter from the norm).
Hopefully this can be fixed in a future release; I certainly understand how features and bug fixes have their own priorities. Thanks again for OmniFocus and have a great holiday!
