Tie multiple projects to one request

[rwinslow]

Is it possible to tie multiple projects to one request? 

[skyehansen]

I think resolving IDs are a 1:1 relationship, so you would not be able use this route but you would be able to make an external lookup field that is multi select and list all your projects that way. Of course, that is a rather manual thing to do, and there aren't any automations (closing all the projects wouldn't close out the request) so it's up to you as to what your goal is

[rwinslow]

How do I make an external lookup field? If i were to make them this way can info flow backwards from the projects back to reporting tied to the request? 

[jon_chen]

Hello @KellieGardner, 

Looks like @rwinslow had a follow-up question to your response; if you have the time or context to provide an answer, that would be greatly appreciated!

[FernandoFu2]

Possible but one of them is going to appear unlinked to the request.

[KellieGardner]

This is not an option, unfortunately. There are a few tricky ways to work around it. These are ideas I've shared with leadership teams I've worked with:

1. Convert your request to a "parent" project that has milestone tasks and then have those milestone tasks tied to additional projects through cross-project predecessors. 

2. Convert your request to a parent project, create issues for each of the sub projects, and convert those to resolvable projects.

[kautuk_sahni]

@rwinslow Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!