Can company managed projects coexist with team managed projects?

[Nuno Fernandes]

Is it possible to coexist a jira software team-managed project with a xray team managed project where the latter links issues "from outside" or team-managed projects are like air tight bubbles?

Many thanks

Nuno 

[Jack Brickey · Accepted solution]

Hi @Nuno Fernandes , welcome to the community!

I have a number of questions or concerns about your question here. First I note that you have listed this as being on server. If that is the case then TMP projects do not even exist in server. However maybe you are in fact using cloud? The next question I have is what do you mean by "outside"? Are you working with two different instances of Jira? TMP projects are indeed silos in that their schemes configurations permissions etc. are all self-contained. Now I'm not sure about how x-ray works exactly particularly where TMP is concerned however you can do things like create a personal kanban board on your profile against a filter that includes multiple TMP boards.

[Nuno Fernandes]

So true, now that I’ve just searched the documentation for server version: no pages found (because it’s only for cloud). Different projects need to created and the Jira administrators will create the specific issue types for xray (and jira) and they will follow in and out the different project (“outside” standing for the other project in my company but “outside” my team).

I'm just a newbie and this is the first breadcrumb :)

Many thanks,

Nuno

[Laura Engstrand]

I would like to ask the same question but with a different nuance.  

We currently use team based projects exclusively ( not my decision ).  I am advocating to migrate to company based.  Is it possible or advisable to migrate some team based projects to company based and leave a few as project based?  Pitfalls?

thank you.

[Nic Brough -Adaptavist-]

Actually, there's not much in the way of pitfalls.  CMP projects do work differently, and I strongly recommend explaining to the TMP users you migrate that most things will work the same (or intuitively), but the administration is very different.  

One of the reasons I prefer CMP projects is that they simplify reporting - because they share fields, you can more easily report on them.  Imagine you have four projects, two CMP and two TMP.  The CMP projects are sharing a field called Colour, and the TMP projects have the same.  All a select list.

When you try to create a search, the advanced search will autocomplete the name of the field, offering only Colour, but then when you say =, it will offer all the options from all three fields.

Also if you go to the dashboard and add a gadget that works off fields, it will offer all three Colour field and no indication of which two are from the TMP projects. 

If you rationalise on CMP projects, these problems go away - one Colour field, in many projects.

You may want to include that in your migration talk.