I'd need a bit more information about how your teams operate, but I'd expect just creating a new Jira Project with the same Schemes used on your current Project would be easiest. You could try using the Component/s field, but this seems to never end well. You end up with a messy list of Components, people don't use the field correctly, etc.
Generally most people that we work with find that having their team work from multiple Jira Projects works best. It adds a bit more complexity, but it gives you a ton of flexibility. For example, when your outsourced QA team needs to work on Jira issues, you can easily grant them access only to the Project they need access to, rather than letting them see everything and just work off a Component.
Provide a bit more detail about what you're doing and want to accomplish and we should be able to come up with a good solution!
![Dave Theodore [Coyote Creek Consulting]](https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/557058:a1f94001-e8c1-4ab0-95d3-01a204687231/254ecf19-a9ab-40df-9b8a-51a3251ea418/128 "Dave Theodore [Coyote Creek Consulting]"){kind=avatar}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.