-
Suggestion
-
Resolution: Fixed
-
None
-
6
-
Issue Summary
I was dismayed to read in JSDSERVER-4382 that in 4.7 all new requests will be private.
Our JSD portal, which services over 200 external client companies whose issues must be hidden from each other, is specifically crafted to to require that the Organization MUST be specified and this works well in pre-4.7.
This change is going to confuse our external users who will get an error that not all fields are filled in and they must choose organization. But that field is not labeled Organization (at least it's not in our current version). I know this because for our few end users that work for more than one organization, which sets requests to Private by default, explaining to them what the error message means and how to set the organization field, has been quite daunting.
Please make the default to have the Org set or Private configurable by project.
Workaround
Please note that it is possible to disable the new behavior introduced in the Customer Portal in JSD 4.7.x by following the steps below:
- Navigate to the following page to access the Dark Features page:
<baseUrl>/secure/admin/SiteDarkFeatures!Default.jspa
- Enter sd.customer.share.default.private.disabled in the field Enable dark feature, click on the Add button, and verify that the dark feature sd.customer.share.default.private.disabled is listed in the page:
After you followed these steps, if a customer is a member of exactly 1 organization, this organization will be automatically selected in the request creation form (as it used to be the case before JSD 4.7.x
4.9.0 Release
Customers can get the pre 4.7 default sharing behaviour back. More details -
https://confluence.atlassian.com/servicedesk/jira-service-desk-4-9-x-release-notes-1005326200.html#JiraServiceDesk4.9.xreleasenotes-sharingiscaring
- is caused by
-
- Closed
- is related to
-
- Closed
- relates to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-6761] Backtrack 4.7 change that makes all new requests private to be configurable per project
| Link | New: This issue relates to JSDSERVER-11058 [ JSDSERVER-11058 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 512836 ] |
| Fix Version/s | New: 4.9.0 [ 91520 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Link |
New:
This issue is related to |
| Description |
Original:
h3. Issue Summary
I was dismayed to read in Our JSD portal, which services over 200 external client companies whose issues must be hidden from each other, is specifically crafted to to require that the Organization MUST be specified and this works well in pre-4.7. This change is going to confuse our external users who will get an error that not all fields are filled in and they must choose organization. But that field is not labeled Organization (at least it's not in our current version). I know this because for our few end users that work for more than one organization, which sets requests to Private by default, explaining to them what the error message means and how to set the organization field, has been quite daunting. Please make the default to have the Org set or Private configurable by project. h3. Workaround (!) Please note that it is possible to disable the new behavior introduced in the *Customer Portal* in JSD 4.7.x by following the steps below: - Navigate to the following page to access the Dark Features page: {code:java} <baseUrl>/secure/admin/SiteDarkFeatures!Default.jspa {code} - Enter *sd.customer.share.default.private.disabled* in the field *Enable dark feature*, click on the *Add* button, and verify that the dark feature *sd.customer.share.default.private.disabled* is listed in the page: !DarkFeature.png|thumbnail! After you followed these steps, if a customer is a member of exactly 1 organization, this organization will be automatically selected in the request creation form (as it used to be the case before JSD 4.7.x |
New:
h3. Issue Summary
I was dismayed to read in Our JSD portal, which services over 200 external client companies whose issues must be hidden from each other, is specifically crafted to to require that the Organization MUST be specified and this works well in pre-4.7. This change is going to confuse our external users who will get an error that not all fields are filled in and they must choose organization. But that field is not labeled Organization (at least it's not in our current version). I know this because for our few end users that work for more than one organization, which sets requests to Private by default, explaining to them what the error message means and how to set the organization field, has been quite daunting. Please make the default to have the Org set or Private configurable by project. h3. Workaround (!) Please note that it is possible to disable the new behavior introduced in the *Customer Portal* in JSD 4.7.x by following the steps below: - Navigate to the following page to access the Dark Features page: {code:java} <baseUrl>/secure/admin/SiteDarkFeatures!Default.jspa {code} - Enter *sd.customer.share.default.private.disabled* in the field *Enable dark feature*, click on the *Add* button, and verify that the dark feature *sd.customer.share.default.private.disabled* is listed in the page: !DarkFeature.png|thumbnail! After you followed these steps, if a customer is a member of exactly 1 organization, this organization will be automatically selected in the request creation form (as it used to be the case before JSD 4.7.x h2. 4.9.0 Release Customers can get the pre 4.7 default sharing behaviour back. More details - [https://confluence.atlassian.com/servicedesk/jira-service-desk-4-9-x-release-notes-1005326200.html#JiraServiceDesk4.9.xreleasenotes-sharingiscaring] |
| UIS | Original: 5 | New: 6 |
| UIS | Original: 6 | New: 5 |
| UIS | Original: 5 | New: 6 |
As of 4.9.0, the sharing setting has been fixed to also work on the customer portal.
Customers relying on the sharing behaviour of versions before 4.7 can now get that out of the box by turning off the setting. Details here -
https://confluence.atlassian.com/servicedesk/jira-service-desk-4-9-x-release-notes-1005326200.html#JiraServiceDesk4.9.xreleasenotes-sharingiscaring
I have created a separate ticket to track if there is value in having this configuration on project level.
https://jira.atlassian.com/browse/JSDSERVER-6856