-
Bug
-
Resolution: Answered
-
Medium
-
None
-
None
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
The articles from https://confluence.atlassian.com/servicedeskcloud/serving-customers-with-a-knowledge-base-732528995.html is misleading users , and there are not sufficient guide/steps on configuring this. As this will need further configuration on Confluence side to ensure that the functionality "Allow all active service desk users and customers" to works properly. This has lead to creation of bug ticket created in JAC due to the confusion that occurs:
https://jira.atlassian.com/browse/JSD-3448
If you choose to restrict viewing of the linked Confluence space to licensed users, you must grant customers a Confluence license or open your Confluence space to anonymous access.
Which I have broken down to below:
If you choose to restrict viewing of the linked Confluence space to licensed users, you must grant customers a Confluence license (this is correct)
If you choose to restrict viewing of the linked Confluence space to licensed users, you must open your Confluence space to anonymous access ( this is not correct, why would you want to open Confluence space to anonymous access if you would like to restrict it?)
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
TESLA-538 Failed to load
[JSDSERVER-3617] Misleading doco for KB setup in Service Desk
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304470 ] | New: JAC Bug Workflow v3 [ 3125647 ] |
| Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 2058591 ] | New: JSD Bug Workflow v5 - TEMP [ 2304470 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2056028 ] | New: JSD Bug Workflow v5 [ 2058591 ] |
| Workflow | Original: JSD Bug Workflow v5 [ 1956310 ] | New: JSD Bug Workflow v5 - TEMP [ 2056028 ] |
| Workflow | Original: JSD Bug Workflow v4 [ 1615793 ] | New: JSD Bug Workflow v5 [ 1956310 ] |
| Description |
Original:
The articles from https://confluence.atlassian.com/servicedeskcloud/serving-customers-with-a-knowledge-base-732528995.html is misleading users , and there are not sufficient guide/steps on configuring this. As this will need further configuration on Confluence side to ensure that the functionality "Allow all active service desk users and customers" to works properly. This has lead to creation of bug ticket created in JAC due to the confusion that occurs:
https://jira.atlassian.com/browse/JSD-3448 !Selection_117.png|thumbnail! *_If you choose to restrict viewing of the linked Confluence space to licensed users, you must grant customers a Confluence license or open your Confluence space to anonymous access._* Which I have broken down to below: If you choose to restrict viewing of the linked Confluence space to licensed users, you must grant customers a Confluence license (this is correct) If you choose to restrict viewing of the linked Confluence space to licensed users, you must open your Confluence space to anonymous access ( this is not correct, why would you want to open Confluence space to anonymous access if you would like to restrict it?) |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-3617]. {panel} The articles from https://confluence.atlassian.com/servicedeskcloud/serving-customers-with-a-knowledge-base-732528995.html is misleading users , and there are not sufficient guide/steps on configuring this. As this will need further configuration on Confluence side to ensure that the functionality "Allow all active service desk users and customers" to works properly. This has lead to creation of bug ticket created in JAC due to the confusion that occurs: https://jira.atlassian.com/browse/JSD-3448 !Selection_117.png|thumbnail! *_If you choose to restrict viewing of the linked Confluence space to licensed users, you must grant customers a Confluence license or open your Confluence space to anonymous access._* Which I have broken down to below: If you choose to restrict viewing of the linked Confluence space to licensed users, you must grant customers a Confluence license (this is correct) If you choose to restrict viewing of the linked Confluence space to licensed users, you must open your Confluence space to anonymous access ( this is not correct, why would you want to open Confluence space to anonymous access if you would like to restrict it?) |
| Link |
New:
This issue relates to |
| Workflow | Original: JSD Bug Workflow v2 [ 1602962 ] | New: JSD Bug Workflow v4 [ 1615793 ] |
| Workflow | Original: JSD Bug Workflow [ 1398847 ] | New: JSD Bug Workflow v2 [ 1602962 ] |
| Component/s | New: Knowledge Base [ 26195 ] |