Summary

Creating Space and Linking it to the Jira service desk as a KB then removing it from Jira service desk will not reset Space permissions and Jira service desk users will be able to access the space with correct url.

Environment

• Service Desk 3.8
• Confluence 6.4.1

Steps to Reproduce

Varian 1

1. Create space TEST in Confluence and
2. Log in to Confluence with Jira Service desk customer (unlicensed).
3. You will not be able to see space TEST even using direct URL to the space.
4. Link the same space in JSD as a KB
5. Log in to Confluence with Jira Service desk customer (unlicensed).
6. You will be able to see whole Space.
7. Unlink the space in JSD.
8. Log in to Confluence with Jira Service desk customer (unlicensed).

Variant 2

1. Create space TEST-A in Confluence and link it to JSD Project A
2. Create space TEST-B in Confluence and link it to JSD Project B
3. User A is Customer at JSD Project A
4. User B is Customer at JSD Project B
5. User C is Customer at JSD Project A & B

Expected Results

Variant 1

1. You will not be able to see space TEST even using direct URL to the space.

Varian 2

1. User A should be able to access Confluence KB A only (as he is not a customer of JSD project B)
2. User B should be able to access Confluence KB B only (as he is not a customer of JSD project A)
3. User C should be able to access Confluence KB A + B

Actual Results

Variant 1

1. User will be able to see whole Space.

Variant 2

1. All Users will be able to see both spaces Space.

Notes

New spaces are not affected by permissions. Only newly linked ones.

Workaround

No known workaround at the moment.