Exporting or emailing tasks in the desktop or Mac version is simple. With AppleScript you can pretty much do whatever you want.

The capability does not exist in the iPhone version. It does exist in the iPad version albeit rudimentary where you can only email a single task one at a time. One needs to be able to send a list of tasks at once.

But emailing is the most basic means of sharing tasks and is not especially good for real collaboration. There needs to be some sort of server connection and the ability to share server records through a cloud connection.

[QUOTE=JohnJ80;112463]Exporting or emailing tasks in the desktop or Mac version is simple. With AppleScript you can pretty much do whatever you want.

The capability does not exist in the iPhone version. It does exist in the iPad version albeit rudimentary where you can only email a single task one at a time. One needs to be able to send a list of tasks at once.

But emailing is the most basic means of sharing tasks and is not especially good for real collaboration. There needs to be some sort of server connection and the ability to share server records through a cloud connection.[/QUOTE]

The bottom line here is that an expensive software product for task/project management does not permit native delegation without someone tinkering around the edges. I'm not messing around with AppleScript to fix what is a serious defect (IMHO). This is the first time we have had a 'leaver' in the team so we had never had to address this before.

[QUOTE=JohnJ80;112449]I don't understand why this is so low on the features priority list.[/QUOTE]

It's relatively high on the priority list, actually. It's just that the number one task is a very big one. (A new, more modern interface is by far the most common request we get for the Mac app.) As/after we complete that task, we've got a lot more freedom to work on other things.

With regards to this specific feature, there's probably also a bit of a chicken-and-egg thing going on, to be honest. Because the existing app was designed around a single-person workflow, there are a large number of customers that use it that way and request features they'd like to see. For example, Forecast view and requests for more repeat patterns both have more than twice as many requests attached as delegation does.

None of the above should be read as discouraging folks from requesting this - or other features they want, for that matter. Quite the opposite! It's going to be a while before we'll have anything visible to show for the work we're doing now, but feedback we get during that process still matters.

Forgot to mention, updated the appropriate items in our development database appropriately. Added Landsharks' request for task emailing, for example - several of the recent posters had existing requests for the things they want in there already.

Here PERTy PERTy, here PERTy PERTy... where is the PERT?