Hi all,
I'm trying to add the "Reporter" field in the form used by a customer to submit a request. It is necessary form me because a customer could open an issue raise by a collegue.
Is there any way to do that? I tried to follow the guide without success.
Thanks
It is not currently possible for a customer to raise a request on behalf of another customer. What is an open suggestion for this that you may want to watch and vote for - JSDCLOUD-4102 - "Raise this request on behalf of" for customers?
The best option would be to leverage the request participant field where are the reporter can actually include another customer if you have the project configured to allow that.
you can as an agent simply click on the Reporter field and change it if desired.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Users who have permissions to be only "Customer portal", cannot indicate another person to be "Reporter" of the issue.
This permission is only available to users who have a "jira-service-management" license within the environment, which allows them to access Jira internally and manage the portal's clients when opening issues.
In that case, there are two suggestions:
The user who will open the issue, after opening it, can share the ticket with his colleague and he will have visibility about it.
You can start working on the concept of "Organizations" in some clients and start organizing them into blocks, so whenever a client within the "Organization" opens the issue, he can choose whether to automatically share it with others.
A different solution would be for you to change the reporter internally within Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Fernando,
thanks for your reply. We need to enable a customer to set the field "Reporter" because we want to organize the customers allowing only a few of them (the team leaders) to open issues but we also want to trace who raised the issue.
In which way can I change the reporter internally within Jira?
Where can I find the full list of fields a customer can edit?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
man
In order for you to enable a client user to edit you need to give this client internal permission in your environment as a "jira-servicemanagement-user".
After that, you need to go to "Project Settings" > Screens > Select the "Screens" set of the issuetype and add the "Reporter" field in the "Edit" and "View" screens.
After that, internally through Jira, the client just needs to access the issue and click on the "Reporter" field to change the value of the field.
An interesting point:
If only team leaders can create issues, you could make only those team leaders a customer of your project.
But if any user can open an issue and you want to put it in the leader's name, try to act with an automation, in this idea:
Create a user selector custom field named "Team Leader".
Place this field in the customer portal so that the user, when opening the issue, fills in the "Team leader" field.
Then create an automation to change the issue reporter to the user present in the "Team Leader" field.
Here's an automation structure:
Please rate the best solution for your case and let me know if you have any questions :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, Jack!
I believe that Vicenzo's idea here is to put only one "Team Leader" to license internally in Jira and this change the "Reporter" of the issues.
Aiming at this concern with a licensed user and other accesses that this can compromise, I suggested the use of automation to change the value of the reporter through a custom field available on the customer portal. I believe this is the best case scenario for his situation or making only the team leads customers for his project.
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.