-
Suggestion
-
Resolution: Unresolved
-
414
-
3
-
NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? 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
-
- Closed
- is related to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDCLOUD-4102] "Raise this request on behalf of" for customers?
JSM. It's now 2024 and people are still requesting this feature. Please look into this more effectively than having come up with work arounds, making MORE custom fields and MORE automations. We shouldn't have to add more of these just to say, "Hey, my coworker can't log into his computer so he can't create a ticket." And the Modify Reporter permission that says, "Ability to modify the reporter when creating or editing an issue." is misleading because that just doesn't work on the front end, portal, which is where we need it.
This is an essential feature for allowing clients and their third parties, like SEO companies, to raise tickets on behalf of one another where necessary. If an SEO expert works with multiple clients of ours, they have to be sure of raising tickets for the correct company. It's too easy for a user in multiple organisations to select the wrong one or omit it altogether. If they have to search for the email of another user in their organisation, they're less likely to make a mistake and we can more easily find those tickets.
I come to your same conclusion but I could not make it working. If you can explain the steps in how you achieved that, it would be much appreciated.
M
addendum: I did solve it . . . I needed a coffee break 
Also voting for this one.
This is huge for us, for managers opening on behalf of their employees, for employees opening on behalf of their managers, for key users of certain applications that all of a sudden we need a license for, just so they can raise tickets on behalf of the standard user that has the problem...
And no, adding them as "watchers" is NOT a solution - the actual, relevant notifications would still also arrive to the original opener, and there could be GDPR implications as well due to data privacy (HR also uses our Jira instance).
what about to enclose a form to the request with some user picker field which normally cannot be added to the screen on portal? Doing the same for version picker field and similar types not allowed on portal. You just map the "form" field to Jira field on backend and it works perfectly even for priority and such...
I am voting for this feature considering that we are using a lot of automation with assigning assets to INsight.
Would like to see this. Same reasons as mentioned above. Need admin staff to be able to open tickets on behalf of other users.
I would also echo this request and add my vote in favor of this capability for our customers.
This feature is definitely needed and I can see that a workaround has been issued which really isnt the answer. see link below:
https://community.atlassian.com/t5/Jira-Service-Management/Can-a-customer-create-a-request-on-behalf-of-another-customer/qaq-p/948398
Is there a usergroup where we can raise issues like this or how do we escalate to Senior managers in Atlassian? I'm surprised that this ticket was raised 8 years ago!