-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Currently, the 'Browse Project' permission is needed in addition to the 'Modify Reporter' one for internal users to be able to raise requests on behalf of customers.
Users should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission.
This is needed because there are cases when users shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers.
- links to
Form Name |
---|
[JSDSERVER-11077] Allow users without 'Browse Project' permission to raise requests on behalf of customers
Support reference count | New: 1 |
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 978010 ] |
Description |
Original:
Currently, the '{*}Browse Project'{*} permission is needed in addition to the 'Modify Reporter' one for licensed users to be able to *raise requests on behalf of* customers.
Users should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission. This is needed because there are cases when users shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers. |
New:
Currently, the '{*}Browse Project'{*} permission is needed in addition to the 'Modify Reporter' one for internal users to be able to *raise requests on behalf of* customers.
Users should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission. This is needed because there are cases when users shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers. |
Description |
Original:
Currently, the '{*}Browse Project'{*} permission is needed in addition to the 'Modify Reporter' one for internal users to be able to *raise requests on behalf of* customers.
Internal users should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission. This is needed because there are cases when internal users shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers. |
New:
Currently, the '{*}Browse Project'{*} permission is needed in addition to the 'Modify Reporter' one for licensed users to be able to *raise requests on behalf of* customers.
Users should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission. This is needed because there are cases when users shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers. |
Description |
Original:
Currently, the '{*}Browse Project'{*} permission is needed in addition to the 'Modify Reporter' one for agents to be able to *raise requests on behalf of* customers.
Agents should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission. This is needed because there are cases when agents shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers. |
New:
Currently, the '{*}Browse Project'{*} permission is needed in addition to the 'Modify Reporter' one for internal users to be able to *raise requests on behalf of* customers.
Internal users should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission. This is needed because there are cases when internal users shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers. |
Summary | Original: Allow agents without 'Browse Project' permission to raise requests on behalf of customers | New: Allow users without 'Browse Project' permission to raise requests on behalf of customers |
Description |
Original:
Currently, the '{*}Browse Project'{*} permission is needed in addition to the 'Modify Reporter' one for agents to be able to *raise requests on behalf of* customers.
Agents should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission. This is needed because there are cases when agents shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers. |
New:
Currently, the '{*}Browse Project'{*} permission is needed in addition to the 'Modify Reporter' one for agents to be able to *raise requests on behalf of* customers.
Agents should be allowed to set the Reporter of the tickets they create, even if they don't have the 'Browse Projects' permission. This is needed because there are cases when agents shouldn't have access to all the tickets in a project, however it's required for them to create new requests on behalf of customers. |