Is there a concept of a "sub-project" in Space? Or how else might I create dependencies between projects?

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?

0
2 comments

Mark Norgate hi!

I believe the best fit for this will be the cross-project issue board solution. We have task in our backlog to implement this feature in Space. Unfortunately, there is no ETA for it at the moment. Feel free to subscribe to the YT ticket below to get further updates:

https://youtrack.jetbrains.com/issue/SPACE-13220/Cross-project-or-team-wide-issue-board

 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?

Currently, there is no way to create dependencies that way. However, you can check the solution with attaching/detaching the Space git repositories. This might help to make the "parent" repo available for other projects. But still won't help to avoid making issues more atomic.

0

While there is no direct concept of a "sub-project" in Space, you can create dependencies between projects by referencing issues from one project in another. For example, if you have an issue in the "parent" project that is related to an API in another project, you can create a link to the relevant issue in the "child" project. This will allow you to track dependencies between projects and ensure that issues are being addressed in the appropriate context.

0

Please sign in to leave a comment.