How to prevent linking issues between company managed and team managed boards

LIS Guy

Greetings,

 

is there a way to prevent the linking of issues from a team managed board to an issue in a company managed board and visa verse?

 

I like to do it, because we are using company managed projects for everyhting "official" in our PI Plannings and Sprints, but I want to give our users the option to use Jira Boards also for other topics of daily work life.

But What I don't want is that people stop working in the PI relevant boards, because it might be easier for them to just use the team managed boards (less rules, more flexibility on their own, own automations etc...).

So, is there a way to prevent it?

Global Automation?
Permissions?

 

Thanks in advance

LIS Guy

I've found a solution.

It's probably not THE solution, but for now it's working.

 

It's a two part solution.

Part one: There is a custom field in the company managed projects input mask. This field is read only.

 

Part two is a also a global automation.

It compares the mentioned custom fields in the destination and issue with each other.

Since team managed projects don't have the custom field and company managed projects can't get rid of it, you can now only link issues with each other when either both HAVE the custom field or both HAVE NOT the custom field.

The just linked issue will be revoked (deleted) 1,2 seconds after it has been created.

This would all be so much easier, when I could read out the project type in Jira. For now I could not find a way to read it out or filter it (I mean the "company managed" or "team managed" category).

 

Thanks.