I am really enjoying playing around with Space, but one thing I am seemingly unable to do is to address repos in one project from another when creating issues.
I could very easily reorganise things such that the issues are more atomic. But I have a website whose code is in one repo in what conceptually is the "parent" project, but that is the front end for many other projects. So there are other projects that have many repos for functionality of the APIs and other back ends, and it makes sense to me that issues should address both the front end repo, which exists in another project, and the repo in the current project, which has the API supporting one aspect of this monolithic API.
So what pattern would be most useful to adopt? Can one project be a child of another, and inherit its repos? Or is there a way to create dependencies between projects on issue boards?