-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Low
-
Component/s: Knowledge Base & Confluence integration
-
None
-
1
-
Severity 3 - Minor
Issue Summary
After changing the space key in Confluence, Jira service management user is unable to edit knowledge base articles.
Steps to Reproduce
- Open Confluence > create Space, set spaceley AAAA
- Open Jira Service Management project > link space AAAA as knowledge base, set as following.
- Who can view: A;; logged-in uses
- Who can edit: Service project users
- Confluence > space AAAA > space settings > space detail > change space key from AAAA -> aaaa1
- Create UserA with JSM User license without Confluence license.
- Login as UserA > JSM project > open KB article on space AAAA
- UserA can see article, but can't find "edit" button.

- Login as admin, and revert the spacekey of Confluence space from aaaa1 to AAAA(original).
- UserA can see edit button on KB articles.
Expected Results
After changing the space key in Confluence, JSM licensed user can edit KB articles.
Actual Results
After changing the space key in Confluence, JSM licensed user can't edit KB articles.
(If the user has JSM User and Confluence User license, the user can see edit button on articles.)
additional info
After changing spacekey, KB article URL contains original spacekey.
sample: https://domain-name.atlassian.net/jira/servicedesk/projects/projectkey/knowledge/articles/354582564?spaceKey=AAAA
But Confluence page URL contain new spacekey.
sample: https://domain-name.atlassian.net/wiki/spaces/aaaa1/pages/354582564/
KB article URL should be changed to new spacekey.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Or, Revert the space key of the Confluence space to the original key.
- duplicates
-
JSDCLOUD-15744 "Restricted Content" error when trying to create a new KB article on JSM after renaming space keys on Confluence
-
- Closed
-