While a customer can’t open on behalf of another customer they can add as participant so they would see updates.
Try this workaround:
We created a custom field called "Affected User" and added it to the forms. Support is trained to look at that field and not the reporter field.
We also added automation that automatically shares the ticket with the Affected User to make sure they get the notifications and can monitor the ticket in the portal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's certainly an option, however, I would really like to figure out how to make "Reporter" work so that running reports and looking at metrics based on users opening tickets will be consistent. We've been running for a while and reports would be mixed between "reporter" and "affected user" fields
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Synngul
We setup the custom field and then added it, as a required field, on all of the forms we created.
When: Value changes for (select your custom field)
If: Compare two values
{{issue.reporter.name}} does not equal {{issue.customfield_####.value}}
(you'll have to find your custom field ID)
Action: Edit issue fields
Choose "Request participants" as the field to set
Add (select the custom field you made) from Current issue
We threw a "re-fetch" action in there, too, because it wasn't working without it, for some reason.
It's been working for us , with no issues, for 2 months.
I hope this is helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I used this method to set the reporter, instead of request participants and it worked and bypassed needing to give everyone a JSM license.
I set it up as follows, and it didn't require the re-fetch of data and still ran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Let Atlassian Know! Please vote/comment. There is clearly a need
[JSDCLOUD-4102] "Raise this request on behalf of" for customers? - Create and track feature requests for Atlassian products.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, you can create an issue on behalf of the other users as long as the user is part of the organization on the service desk.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bryan,
how did you achieve this? I can't manage to set it up so that customers can create requests on behalf of others, even when being part of their organization.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was also under the impression that only agents could create issues on behalf of other users. Would be very interested if there was a way around this!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My scenario is having a 1rst level support front answering the telephone and opening requests on behalf of customers calling in. They wouldn't necessarily need access to Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, you're probably right @Carol Jones, I haven't take into account of me being the agent, it was my bad.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
correct. The portal does have the open on behalf of if you are an agent but the option is not presented if you are a customer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jack Brickey how dept name can appear of the customer?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.