You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
Please vote for this functionality: https://jira.atlassian.com/browse/JSDSERVER-328
Or for Cloud: https://jira.atlassian.com/browse/JSDCLOUD-328
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:
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Create an automation script which is triggered by issue assign and add a comment with assignee name to the issue visible to your client:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
Victor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Mathias,
Unfortunately no. See the topic on the same link
victor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
my guess is because it humanizes the servant on the other side, which is unacceptable for jira's biggest clients
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.