Hi there,
We are big users of Confluence (Server/DC), and we sometimes have a space dedicated for some of our products, where the users will find user guides and other troubleshooting articles.
We are now deploying JSM , and we don't want to have a project per solution for the support... We will have only one team to do the support, but they may have to capitalize on users guides writen on several spaces.
As we cannot link a JSM project to several Confluence Spaces, what will be the best approach for you taking in consideration that we already have a lot of documentation on several spaces ?
Thanks a lot for your advices!
@Patrice Champet is all the information public and by that I mean does it matter if users in the service desk see or can search multiple user guides? On our server instance, we had to combine our different support spaces into one so it was searchable in the Service Desk. I know some companies that have a since desk and they have everyone go to the help center to search for answers. They then create dummy service desks that link to the different confluence spaces and filter up to the help center level. This is a workaround but we found that having them in a single space worked best for us. You should also vote for https://jira.atlassian.com/browse/JSDSERVER-170 They then might bring this to enterprise.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.