Is it possible to add custom fields or a field like 'Due date' to the customer views? We would like to share for example the 'Due date' of an issue with the customer. As far as I can see, we cannot influence the issue interface that the customer sees on the portal...
Thanks in advance!
I think you misunderstood the question. He was not asking how to add the field to the FORM. He was asking how to show the field to the Customer on the portal.
I have the same issue. My form asks a number of standard questions like Priority, Due Date, etc. However when the customer views the Request on the Customer Portal they do not see it.
This seems like such a basic feature, why would you show them the questions on the form, but not let them see them in the Portal.
I have the same question. To be clear, ALL fields that you add "to the form" will naturally appear on the portal - but there are fields that our customer service staff complete on the second tab of the issue, not intended for the customer to complete. For example "Criticality". We don't want the customer to complete these fields on the form. However, we'd like them to appear on the Customer Portal in order to provide that information back to the customer. I hope this makes sense.
Bryan, this is NOT an open ticket for this feature. This link is for "As a customer , JIRA Service Desk Customer Portal displayed Date format as per configured in JIRA"
The topic we are discussing here has to do with custom fields that the customer does NOT populate on the portal, but are used internally (by the service desk team, for instance) to process and update the status of the request.
I used an example, "Criticality". Our team uses that field to asses the issue and process it accordingly. The customer would like to see this field on the portal when they check the progress of the issue - but because it isn't a field on the initial form, it's not available for the customer to see., and there's no means to post it to the portal for viewing purposes.
(1) Add the field to the submission form, which makes it show up on the portal issue page later. The obvious problem is you then imply to the customer that they have control over the field and they're supposed to put something in there when they submit the issue. You can work around that some with tooltips like "leave blank -- not for customer use" and then automation that erases anything they submitted after they create it.
(2) If you've got a small, binary, piece of information you can overload the workflow statuses with it. We have one for escalating an issue that should really be a separate field, but instead it's a workflow status. If you've got a really simple workflow like Open --> In Progress --> Done you can change that to Open / Escalated / In Progress / In Progress and Escalated / Done and set up the transitions as makes sense. I do other things for binary information like "this issue has been estimated to be over a certain size and will take longer" as a workflow status (summarized as "Heavy"). Automation adds a comment when it is put into that status. So for a while the status is "Heavy" instead of "Open", but eventually it gets moved into "In Progress" so "Heavy" is no longer visible, but by that time they've seen it on the status for a while so probably remember, and the information that it's a bigger-than-average issue is visible somewhere in the comment thread.
But, again, I with they would just let you show extra fields on the portal. These workarounds are far far from perfect.
I didn't require any extra plugins to do this.
I found this plugin in marketplace they have ability to display the fields but I didn't try it yet.
As Ert Dredge mentioned above, and I'm still waiting for, this should be an out-of-the-box feature over a plug-in that would cost hundreds of dollars to purchase and yearly renewal fees.
"It's an open feature request to support this. See
Jira does not have this feature by default. For Jira Cloud users, we have developed an add-on called Extra Fields for Jira Service Desk
Using this add-on you can display any Jira field to customers. They will be able to view but not edit the field value. It also supports custom fields. Give it a try and let us know if you face any issue.
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