Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,293,245
Community Members
 
Community Events
165
Community Groups

Best Practice for Change Management across several teams

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

1 comment

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?

Comment

Log in or Sign up to comment
TAGS
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

148 views 0 4
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you