Can an issue be in one project and its tasks in a different project?

[Christina Wilkerson]

We have distributed development teams and would like each team to have their own project (therefore their own individual backlog).  We have a workflow where development of an issue is done in one region however there are deployment tasks in two other regions.  We would like the issue to live in Region A but from that issue, spawn deployment tasks (of that issue) to Region B's project and Region C's project.  Is this possible?

[Nic Brough [Adaptavist]]

You can (with code) spawn issues in other projects.

Sub tasks always belong to their parent, and hence must be in the same project as their parent.

[Christina Wilkerson]

Nic - do you have sample code or could you point to where an example would be?  Thanks!