I'm configuring our new premium instance of JSM.
Our product development teams need to each have a separate project for their product, but we do need transparency and visibility across the 5 product dev. teams, as sometimes an issue can affect other products. If all 5 of these projects belong to the same product category can this provide that visibility that they can all see each other projects, or would I have to add all devs to all projects for that?
Just to answer to your question first and foremost: project category does not impact access to projects in any way. It is mainly useful to:
To specify the last statement: you can search for issues in projects sharing a project category like this:
Category = "Product Development"
Project in ("Product A", "Product B", "Product C", "Product E")
and so on.
To manage permissions, you set this up separately for each project.
On a side note - if you are setting op Jira for product development, are you sure you want to set up JSM rather than Jira Software? That question does not have impact on your question about project categories and permissions, but it does in terms of functionality.
Thanks @Walter Buggenhout _ACA IT_ :)
OK, so is there a way that I can provide access for each of these projects to view each others service desk projects issues and comment internally to enable visibility and collaboration between these 5 projects, but still be able to keep them as individual team projects for the purpose of reporting and notifications?
We are considering next step JS for product change development, however JSM is good for us now for internal business and technical support. So these product dev teams are picking up incident & service request support from the business customers for their products.
You basically set up 5 different projects. In each project you grant access to your users in Project Settings / People by assigning them to the Service Desk Team role.
Hope this helps,
Thanks @Walter Buggenhout _ACA IT_
I think I am understanding that you are suggesting adding all devs to all projects that they need to be able to search and view issues, but to use project permission schemes to define permissions on what each agent can do within each project? Is that right?
Appreciate your help :)
Your JSM project already have a permission scheme where - by default - the permissions to collaborate internally are granted to the Service Desk Team role. Assigning your internal people to that role will grant them the permissions they need.
One caveat though - which is why I mentioned Jira Software. Your users need a license to collaborate. That may be a JSM license, which grants them agent permissions automatically as well. If you only purchased JSM, then that's what you'll have to work with. Or that may be a Jira Software license. Users with a JSW license that you add to the Service Desk Team role in a JSM project will have limited permissions (view tickets, comment internally mainly). That is the setup usually applied for developers.
Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...
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