I am really frustrated to see, that this minor adjustment, that is important for many customers is not implemented yet. AFTER 10 YEARS. I can't belive it! We need it for our workflow in Jira-Datacenter. Thank you for poor customer service.

+1 Please!

Is there any update on this 

+1 Please 

+1, our users require to know who is an assignee to the task. It's gotta be there.

Please allow this to happen. Yes, it seems like it's a silly thing, but we get this request pretty frequently from our internal users/customers.

+1 Please 

An important feature; Connecting Reporter and assignee will save the work time and follow up waiting time.

Thanks for including this in the 4.21.x.... the link to the documentation on how this works is broken though.... howeever, you still can get to the documentation by going to the release notes...

Does Atlassian have to make us pay for every little things? Even Salesforce can do all this for free with their license....

Our users are complaining because when they look at the ticket, it looks like it hasn't been assigned and they don't want to have to go into a list of issues to see an assignee against it

This is a BIG problem for our team. People don't know who is working on their task, so they don't know who to reach out to for questions and status updates. When they have no one to reach out to, they make a duplicate ticket and duplicate tickets slow everything down.

this is too basic to be ignored, especially things has changed to become and ITSM level JSM

I agree. This should be standard functionality. It is a basic requirement for the Requestor to know who is working on it.

I agree. This should be standard functionality.

I agree. This should be standard functionality. I am also surprised that this is not baked into the default suite.

You can do this with addons, but why should we have to pay extra for something that should be standard functionality. 

End users must be able to see who is dealing with their requests.

Having the Assignee visible in the customer service Portal will benefit both Customers as well as Help Desk team members by

1. encouraging direct communication between Assignee and Reporter
2. eliminating the need for Customers to contact Help Desk just to find out who is dealing with their issue
3. eliminating the disruption of Help Desk value adding service delivery activities 

So I see both service quality and efficiency benefits for our support services.

Regards, Michael.

I am surprised this feature is not already available out of the box

Yesterday I purchased the feature Bundled and it working fine so far. Hope to see this in Jira in future but I'm good with the addon too. 

This feature is essential to bring more transparency into the ticketing system

Please implement this feature, it is very important.

For a system targeting customer service, the Assignee field seems like top requirement knowing who is helping me.  For both internal and external support, it's important we can portray our support team through a customer portal.  A great customer experience hinges on the expectation of friendly and helpful agents offering a efficient and personable service.

Please help expedite this feature

Thank you

any update on this feature request?

again seems a basic feature.

Its 2020 and still waiting for this feature. Please, consider developing it asap!

Hi All 👋
We've recently released this feature as a part of the Feature Bundles for Jira Service Desk. This is a new app on the Atlassian Marketplace which bundles useful features for your portal, such us permissions for request types (based on Roles, Groups, Language, Time Zone, and Calendars) or customizable announcement banners. Try 30-day free trial!
In app’s documentation we explain how to show assignee and other additional information on the Request Details View (including sub-tasks, time zones, position in queue, created and updated dates).
Do you need more explanation? Please don't hesitate to contact us via our Customer Portal or book a demo session via Calendly. 🖥
Cheers,

We get a lot of frustration from our customers too for the same reason.

We have been waiting 2 years hoping for this option to be added.

For anyone interested, I found somewhat of a work-around for this. Under Automation you can create a new custom rule that looks like 
https://imgur.com/a/8zcZdjB
Under the "Send Email" option, you can add "User who triggered this action" as a variable and voila!

It sounds very strange and causes a lot of our users frustration when they have to ask in a chat "who is working on my issue?" instead of seeing it themselves. It's very basic functionality. When can we finally get it implemented?

pls add this lol

How did this not make it into the original design, let alone not be implemented five years later? A customer doesn't know who to follow up with on their ticket without this.

For a few orgs in our deployment, this was one of the primary drivers for them to move out of email and into Service Desk:

Portal customers most important question to have answered is the status and who is responsible for the request.

Sort of shocking that this is not possible and even more shocking that this "enhancement" has sat for over 5 years.

It's very sad that this simple feature is not considered by Atlassian by now. We need this feature.

This is very basic but we need this option, please implement this feature.

173 votes for this so far and no responses from Atlassian. 

Our customers are asking for this as well.

This feature seems like a "no-brainer" to implement, just provide the option to not show the assignee for others, who do not want to show.  +1 here!

We should have the flexibility to do this, as admins. I understand the rationale of shielding agents from being bugged by customers, but let us, Admins and Businesses that use your product, decide whether this is something that we need to embrace, or maybe our SD needs to be more open. 

I agree with the comments from a few years ago, this seems to me like it should be a basic feature.  We are a large enterprise and so 3rd party add-ons are difficult to on-board and almost impossible to test at scale as we can not easily generate synthetic traffic which matches our production loads.  I would like to see Atlassian prioritize this request as it seems reasonably trivial to implement thus I am adding my two cents.

amir.katz , guido.santo - thank you guys for valuable advice! We have ScriptRunner and also like it. I'll try both options.

Appreciate your help

I have solved this issue by using the "Automation for Jira" add-on:

https://automationforjira.com/

On every assignee change I post an automated comment like this:

 Your request has been assigned to [user name].

This works well for me.

I ran into the exact same problem. Here's what I did (we have ScriptRunner installed)

1. In the create screen, added a user-picker custom field called 'Assignee - display-only'. It must be defined in the create screen, otherwise it won't be visible in the Customer Portal.
2. Added a script listener on the Issue Assigned event, using ScriptRunner.
3. In the listener, I copy the value from the Assignee field to my custom field.
4. In the Service Desk config, add a help message on the 'Assignee - display-only' field that says it's a read-only field. 
5. The the Create screen configuration, move the custom field to a new tab called 'Read-only fields'. I actually have another field there, 'Issue Links - display-only', which does the same for link, which is another field that Atlassian does not show in Customer Portal.

I'm pretty sure you can create an event listener w/o the ScriptRunner add-on, but this add-on is so useful, it had paid back its cost very quickly (and no, ScriptRunner does not pay me ).

Also desperately need this for internal users. Currently they disappointed because don't know who's working on their request

In our company, agents have close contact with customers and customers know our agents. Would make sense for b2b companies to allow customers to select their agents or at least see who is working on their problems. 

+1, this should be considered basic functionality - especially for Service Desk server where most customers are enterprise environments wanting to manage internal tickets, etc.

Adding my voice, I have just spent way too much time looking for this option as I assumed it would be a given. Administrators should be allowed to set up the customer portal screen just like they can set up the "Create Issue" Screen by choosing which fields to display

I'm just launching a Service Desk project and the first question I was asked from my customers was 'how can I see the assignee?'.

I also think it should be an option, with default=no.

I would say 'just my 2 cents', but we pay much, much more for the Service Desk license

Hi,

Our customers are as well asking for this functionality? Any news?

Regards

We are also using the "Automation for Jira" solution. One tricky spot we've encountered is that the automatic comment means that our "time to first response" SLA is artificially low. Have others run into or worked around this issue?

For those who are facing this situation and are looking for a free workaround solution I would recommend using the "Automation Lite for Jira" add-on. It makes possible to add a comment visible to the reporter on Service Desk Customer Portal and it will show the assignee name. I have created a dummy user and assigned it as a Service Desk Team member, using it as the actor for this automation. The result which is showed to the customer meets the expectation.

Agreed. Customers are getting frustrated with Jira as they are not even able to see who the request is assigned to. They started questioning about JIRA.

Yes, we would need this option too

I agree with the comments above - this should definitely be an option. We should be able to show any fields we want on the customer portal without having to pay third party add-ons for this simple functionality. We also need to be able to show the Assignee to the customer, but also should be able to show any fields. Please update the status of this feature request. Thank you.

Is there going to be a resolution any time soon??

Does it really take 3 years for Atlassian to add a simple field to the customer portal? This should be basic functionality, we the customer should decide what gets shown on the customer portal. Any news on this? I see that this is a trend at Atlassian that they simply ignore all their new feature requests. Ridiculous if you ask me. 

In pluginExtensions for JIRA Service Desk there is an option to show Assignee in customer portal. It is shown on issue next to creator.

Please note that this plugin is not available for Cloud instances. Hence, for Cloud, there is no workaround at all.

In pluginExtensions for JIRA Service Desk there is an option to show Assignee in customer portal. It is shown on issue next to creator.

We would like this feature as we need more visibility towards our end-users.

Any news on this?
Work-around to make assignee visible to the customer?

PS. Sry for deleting link... didn't think i'd have access to delete the link, when i'm not even allowed to visit the link.