Converting a Multiple Deliverable Request to Projects | Community
Skip to main content
H
HeatherRo13
August 7, 2025

Converting a Multiple Deliverable Request to Projects

  • August 7, 2025
  • 2 replies
  • 289 views

Hello! I'm curious if anyone has a best practice, or pros and cons for a request that will result in multiple deliverable projects.

Do you:

A) Convert the same request multiple times and edit per deliveravble?

B) Convert the request to one project, then copy that project to create the additional deliverable projects?

 

Thanks!

2 replies

Madalyn_Destafney
Community Advisor
Madalyn_DestafneyCommunity Advisor
Community Advisor
August 7, 2025

When I used to have to do this, I went with option A because the deliverable projects I was splitting the request up into would need different templates/assignments/etc. and it was easier to do all that when converting it multiple times. If you go with B, you'd likely have to change so much of the project you copied that it wouldn't be worth it. SO, I guess the better question to ask yourself is for your case, which option goes with the least amount of effort to get to the appropriate separate projects/deliverables? Go with that.

If this helped you, please mark correct to help others : )
skyehansen
Community Advisor
skyehansenCommunity Advisor
Community Advisor
August 7, 2025

it depends on your workflow. We have a very specific triaging process that involves the project team being assigned to the request so in this case, we would use the newer "resubmit" functionality to resubmit the request several times and change the deliverable each time. Then everything goes through triage and converted 1:1 with their request.

Terms & ConditionsAccessibility statement

Loading footer...