Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Converting a Multiple Deliverable Request to Projects

Avatar

Level 1

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!

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies

Avatar

Community Advisor

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 : )

Avatar

Community Advisor

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.