I’d like an option in the archiving feature to keep completed actions inside uncompleted projects, rather than moving them to the archive, while still archiving completed projects and completed items in single-action lists. Completed actions in active projects often contain important context that remains useful while the project is still open, and it’s much harder to refer back to them if they’ve been archived too early.
I was just wondering if anyone else would appreciate this feature too.
I think what you’re suggesting is what I was trying to suggest. Perhaps I didn’t word it properly.
Apologies. Reread what you wrote.
I made the same feature request some decades ago.
For background, OmniGroup prioritizes taking tasks off the active board to improve sync speed. The chosen approach is culling, not archiving. I too wish they would be less cavalier about ignoring the distinction. But it seems a few decades has still made no impact in this case.
Don’t know otherwise where my brain was yesterday to have dissed on your post. I’ve deleted my first response.
—
JJW
Thanks for your response. I guess Omni Group doesn’t agree.
OmniFocus was in alpha testing in 2007 and shipped on Jan. 8, 2008, so “decades” is perhaps a bit of an exaggeration….
I too have a preference for the behavior you and Chris would like, but it’s minor. When I use the File > Archive Old Items… command, once or twice a year, I set the “archive” date to about 10 months in the past, which gives me plenty of context. My active database currently has 2070 actions, just over half of which are completed, while my archive file has about 6600 completed actions going back to May 15, 2007.
OK. Pedantic. 15 years or so years ago. Which rounds to about two decades ago. Which, in perception of software turn over, is a few lifetimes.
By comparison, my preference to include true project-only archiving rather than task-level culling is extreme. So much so that I avoid any automatic “archiving” and do it manually by project (a tedious process in all cases).
—
JJW
