-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
125
-
40
-
NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.
I added all of our customers to have the permission "Modify reporter", expecting that this would allow them to see and modify "Raise this request on behalf of" in the Service Desk customer portal. However, according to Matthew's comment towards the end of the comment chain here https://jira.atlassian.com/browse/JSD-1285 , "raise this request on behalf of" is a special field that cannot be seen by non-agents regardless of Reporter modification permissions.
Is there a way to allow our customers to see and modify "raise this request on behalf of"? We have executive assistants who frequently request access and equipment on behalf of executives so this is a must-have for us
- duplicates
-
JSDSERVER-3931 Allow customers to raise requests on behalf of their colleagues.
- Closed
- is duplicated by
-
JSDSERVER-6640 Customers creating tickets from customer portal on behalf of other customers
- Closed
- is related to
-
JSDSERVER-1462 Raise request on behalf of customer through email
- Closed
-
JSDSERVER-3221 Improve Notification for Raising Request on behalf of Customer
- Closed
- relates to
-
JSDSERVER-11016 Documentation does not clearly state that "Raise this request on behalf of" is not available for Customers
-
- Closed
-
-
JSDCLOUD-4102 "Raise this request on behalf of" for customers?
- Gathering Interest
- links to
Hello,
I had the case for some of my support teams who were customers on other services (other projects). I simply managed the permissions associated with the project. Add the support team group to : Service Desk Agent + Modify reporter without adding it to other permissions. It works, without the support team being able to modify another department's ticket.
However, you still need a Jira license to access this field and the list of associated customers. Otherwise, you need to set up an alternative, such as managing an additional field and an automation rule that updates the requester when the ticket is created.
Bearing in mind that releasing this type of access can have quite disastrous security consequences on access to large e-mail lists, this is a subject that Atlassian will be studying with the utmost vigilance.
Regards,