Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
There are numerous discussions about this in the community, but I was unable to find an existing issue for it...
It is extremely common in customer support to want to publish customer-specific documentation. This may include specific contact info, server names/IP addresses, workflow diagrams, support guides, and more. I'm quite surprised that there is no way to do this using the Service Desk/Confluence integration. This seems like a critical piece of that integration. Without it, I'm stuck creating the documentation in another tool and attaching it to a service desk request. Which is very sad. It also won't allow them to search for it easily in the way that KB searches function.
Possible Approaches:
- Allow Service Desk users and organizations to be selectable in the Restrictions of Confluence pages. (This seems like the simplest and easiest to implement to me.)
- Allow linking multiple Confluence spaces to Service Desk, with ability to restrict certain spaces by Organization.
- Others? Please suggest...
Related Community Discussions:
- https://community.atlassian.com/t5/Jira-Service-Desk-questions/Service-Desk-Customer-Portal-Customization-with-customer/qaq-p/697471
- https://community.atlassian.com/t5/Confluence-questions/Customer-specific-Knowledge-base/qaq-p/595217
- https://community.atlassian.com/t5/Marketplace-Apps-questions/Single-Service-Desk-Customer-specific-knowledge-base-s/qaq-p/630004
- https://community.atlassian.com/t5/Questions/Is-it-possible-to-creat-customer-specific-confluence-spaces/qaq-p/599889
Another FR with similar request : https://jira.atlassian.com/browse/CONFCLOUD-53596
https://jira.atlassian.com/browse/CONFCLOUD-57825
Attachments
Issue Links
- is related to
-
CONFSERVER-59168 Customer-specific Confluence pages linked to Service Desk
- Gathering Interest