one or many projects for different customers?

Question

We're just setting up our work flows. We have one core project, and the potential for two or more customers to use the same core project, but to customize the core project in their own ways.

Neither customer will want to share their changes with the other, is there a good process or work flow for a behaviour like this?

Meg Holbrook · Answer

Unfortunately, issues are controlled at the project level, so if security is a problem then you will need to create another project.

There are workarounds for this issue, but it's much easier to manage two projects with these constraints.

Alex McRoberts · Answer

One last issue, which may impact this. We will have customers involved in Project "One" that should not see issues from Project "Two" – vice-versa and neither should be able to see issues from Master Project.

Am I right in saying that issue security will be able to help me here?

Meg Holbrook · Answer

From what I gather here, it seems like you may be better off utilizing one project with 2+ issue types.

Separating by issue type allows the issues across the 'projects' to have the same bones but customization in terms of workflow and fields.

Changing issue types to your 'master' project would require very little modification to your ticket.