It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Customers cannot see Assignee of ticket. They could before but now cannot. What happened?

Customers cannot see Assignee of ticket. They could before but now cannot. What happened? Thanks!

2 answers

1 accepted

0 votes
Answer accepted
miikhy Community Leader Nov 29, 2017

Hi Ian,

There's an open request for this feature in Atlassian's backlog here:

There also is a plugin (mentioned in the thread, called "Extensions for Jira Service Desk") which allows the assignee name to be displayed. I advise you to either try out this plugin or watch the above mentioned request to be notified upon release.


Yeah we have "Extensions for Jira Service Desk" -> Maybe something broke?

"extension-portal-assignee-panel" -> That it? It's def enabled.

Perhaps an update will fix?

"Extensions for Jira Service Desk"

Installed version:5.0.6

Available version:5.1.0

Thanks for your help!

miikhy Community Leader Nov 29, 2017

In that case it seems to be a deeper issue related to the plugin behaviour. I advise you to open a request with InTENSO after reviewing your logs.

Also, of course, getting the last version would help you ensuring you have the latest bugfixes and enhancements available.

AFAIK extension-portal-assignee-panel should work in the version you have installed!

Please also make sure you enabled the Assignee to be displayed as explained in the documentation:

A good debug path would be to ensure you followed all steps (basically enabling display assignee from General setup of the plugin) and checking atlassian-jira.log file for eventual errors if assignee is still not showing!

Let me know if you managed to get it working!

Yup turned out to be issue with that plugin.

"Extensions for Jira Service Desk"

Thanks for you help!

miikhy Community Leader Nov 30, 2017

Glad you’ve found it out!


Unfortunately, since Atlassian does not provide this feature, you cannot avoid using an add-on.

I did this by:

  1. Defined a new custom field [ called Assignee (display-only) ], of type User Picker
  2. Added field to relevant screens
  3. Added a ScriptRunner Script Listener on the issue assigned event.

The script sets the value of the custom field from the value of the issue's assignee.

Important note: setting the custom field is not enough, you must persist the modified in-memory issue to the database with this call:

ComponentAccessor.getIssueManager().updateIssue(null, issue, EventDispatchOption.DO_NOT_DISPATCH, false)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Desk

[New Resource] The Complete Guide to Atlassian for ITSM

Hi Atlassian Community! This is Teresa from the Atlassian team. My colleague Paul Buffington @Buff and I are excited to share a brand new ITSM resource we’ve created – "The Complete Guide to A...

357 views 4 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you