Showing the assignee in the web portal

[Mathias Koprek]

Hi,

Is it somehow possible to see the actual assignee for an issue as a customer in the web portal?

A simple text like "Assignee: Mathias" would be enough.

Kind Regards

Mathias

[Saskia Zeedijk · Accepted solution]

Please vote for this functionality: https://jira.atlassian.com/browse/JSDSERVER-328

Or for Cloud: https://jira.atlassian.com/browse/JSDCLOUD-328

[Susan Hauth _Jira Queen_ · Accepted solution]

Hi Mathias,

We do show the assignee on the Service Desk portal for our internal IT service desk.  BUT it's not OOB, we accomplished it using the plugin:

Extension for Jira Service Desk

[Mathias Koprek]

Hi Susan,

Thank you! I will try that out today!!

[Elisa Lucchini]

Is it still not available? I don't see why we shouldn't display the assignee to the customer.

Usecase in my company: the assignee is the product manager, and the customers are my colleagues, that can report bugs.

And it would be useful if customers could ask their questions directly to the product managers.

[Slava Dobromyslov]

Create an automation script which is triggered by issue assign and add a comment with assignee name to the issue visible to your client:

[Yatish Madhav]

Thanks for this . We did the same ... Not the best workaround. But it has been working for some time.

Another action we have used is the Fetch Issue Data as we have notice sometimes the assignee may have changed by other concurrent automation, etc.

[Magic Mike]

Guys,

There is an answer here : https://community.atlassian.com/t5/Jira-Service-Management/Add-assignee-to-the-customer-portal-page/qaq-p/1462164

It works only in the request list not on a particular ticket.

Best regards,

Mike

[Victor Mutambuki]

Mathias,

It isn't a good practice to have assignee field visible on customer portal.  A number of fields can be added to the request type and given a preset value, but you cannot make them visible on the customer portal:

https://confluence.atlassian.com/servicedeskcloud/configuring-request-types-and-workflows-732528910.html

• Linked issues
• Any fields that are defined by other JIRA applications
• Group, project, and version picker custom fields
• Assignee

Victor

[Mathias Koprek]

Hi Victor,

so even if we and our customers want this "feature" it will not be possible to make it visible on the customer portal?

Kind Regards

Mathias

[Victor Mutambuki]

Mathias,

Unfortunately no. See the topic on the same link 

Hidden fields and unsupported fields

victor

[JP _AC Bielefeld Leader_]

There's a workaround, but you need the nFeed addon. You can create a nFeed custom field, copy the assignee into this field & keep it updated on any changes & then display the nFeed field in the customer frontend.

Still, not best practice to display the assignee on the frontend.

Best

JP

[Jasmijn van den Beukel]

Hi @JP _AC Bielefeld Leader_ could you please help me understand why it is not best practice to show the assignee on the front end? Would be very helpful. 

Best regards, Jasmijn

[Deleted user]

my guess is because it humanizes the servant on the other side, which is unacceptable for jira's biggest clients

[Anthony Fabbricatore]

If best practices were the justification here, then it wouldn't make sense to make it visible on the Requests list as a column -- but it is. This sort of inconsistency bedevils a lot of functionality within JSM.