Hi,
both Wikimedia-Shop and Design exist in Phabricator. Is there a specific reason why a new project is wanted instead of associating tasks with these two existing projects?
(plus potentially using saved queries in Maniphest for "tasks that are design" and "tasks that are not design")

Wikimedia Shop has all kinds of technical tasks. Design project is for the design team. I would like to have a special project for the wikimedia-shop-design so that the designers that work on the shop knew where to look for tasks. It will help me manage the tasks, prioritize and keep track of the tasks that are solely for the shop's design.

I would like to have a special project for the wikimedia-shop-design so that the designers that work on the shop knew where to look for tasks.

I was asking because designers can look for design tasks generally under Design resp. Wikimedia-Design. I only want to add more places to look at if the design team explicitly requested and agreed on a separate project (statement welcome).
This is about "findability" of design tasks and whether a separate project with a workboard for Shop Design is really wanted here, or if designers prefer to manage *all* design tasks (including those ones for the shop) in a broader project instead.

ping? Any news?

@Aklapper I think we found a different solution. Thanks!

What is that solution (as I'm interested in best practices)?

@Aklapper You were right about multiple projects creating more confusion so the solution was not to add one more.