I apologize for not posting an update sooner, I hadn't read this thread since my last post in it, where I said:
Quote:
Originally Posted by Ken Case
Plans can and do change, of course, but we're currently looking at adding this in one of our upcoming 2.x releases.
|
I led off by saying "plans can and do change", and I'm sorry to disappoint but in this case I'm afraid they have: we're no longer looking at adding recurring tasks to an upcoming 2.x release.
Why did this plan change, despite everyone agreeing that recurring tasks would be a useful feature to add?
Apple added a sandboxing requirement for App Store apps which we had to meet before they would approve any new features being added to our app. Implementing sandboxing was a major undertaking, taking about a year out of our development schedule. We finally shipped this sandboxed release last quarter—but even now that we've shipped a sandboxed app,
we're still working through fallout caused by sandboxing.
Of course, sandboxing hasn't been the only thing we've done in the last year: we've also added support for Auto Save and Versions, for viewing scheduling influences, for new constraint types (start no later than, end no earlier than), added print headers to all pages—and on top of that, we've completely rewritten our Microsoft Project import/export code.
But I'm afraid sandboxing has pushed recurring tasks out of the schedule for 2.x. If you'd like to see recurring tasks added to OmniPlan sooner rather than later, please send that feedback to our development team at
omniplan@omnigroup.com so we'll have that feedback readily available as we plan future releases. Thank you!