Best Practice for Change Management across several teams

[Curtis]

We have 3 teams, all which do software/hardware deployments of some sort. Each group is under a different manager. I am looking at JIRA Service Desk, thinking each team should be setup in their own Project. For changes, we have a lot of changes, that potentially affect another team, so they may need to view some changes that may pertain to them.

Is there a way to give someone access to only view one issue type in a Project? In my case would be the change issue type. Or, should each team just have view access to the other groups entire project to all issue types (incidents, problems, etc..)?

Thanks,
Curtis

[Ivan Ferreira]

Hello Curtis! I know this post is very old, but I would like to know how did you finally implemented this scenario. What about creating a new Jira Service Management project only for Change Requests, and make all the stakeholders part of this project?