Thank you for your reply. I think you have the gist of what I’m saying. I guess what I would like is to be able to have a task that is `shared’ between two projects. It seems logical that if one project is reliant/the same as a task in another project/subtask in the same project, one would mark it is a duplicate, i.e. there is one task that needs doing, but is monitored by two different projects. It seems odd then to mark the task as completed and closed as soon as it is duplicated, because then when you look at the progress of the project, it is marked as complete regardless of the status of the original project.
I guess what I’m sort of getting at is project dependencies, which I realize is a premium feature but is there a way just to force the status of that task to track the status of the task from which it was duplicated from. I had a go at the copying solution you suggested, and although useful in certain circumstances, this just clones the task and doesn’t link the two. I think over-use of this feature would lead to multiple duplicates existing across projects, resulting in work being repeated/pausing because people are unaware it has been completed elsewhere…