I am trying to show Fix Version field in customer form but it is not available

[D S]

I have selected Fix Version field in task type fields. Added it to all screens. But it is visible only in Jira, JSD just doesn't show it. 

It doesn't seem to be permission issue, because when i use Jira user in JSD ticket, it also doesn't see this field. 

Is it possible to show this field on a customers screen? 

[Jack Brickey · Accepted solution]

Hi DS, welcome to the Community. This is correct. Fixversion is not a JSD field. You might consider creating a custom field and use automation to copy the value from Fixversion to your custom field and expose that.

[D S]

I tried creating custom field, it appears it jira's forms, but again not in JSD form, although it is added to desired screens. 
May be field should be somehow marked specifically as JSD field?

[Jack Brickey]

Are you talking about adding the custom field to the Create form? that seems sort of odd to me since a value in Fix version would be after the fact. Or maybe you are wanting the customer to enter the version they are on where an issue was seen?

Regardless, if you want a custom field to appear on the form:

• make sure the field is on the create screen. Test that you can see this if you manually create a new issue as an Agent.
• Once you are sure the field exists when creating a new issue then go to Project settings > request types. Find the request type where you wish the field to appear and click Edit fields.
• On the fields screen click add field and you should see the custom field.

[D S]

No, adding field to create screen is easy, it is possible for any field, even version. 

The problem is with the JSD view issue customer form. 

Customer field is available in context field section of specific request type fields. But it will be strange to add this field to create form.

And even if i add this field to create form it is not shown on view issue screen. Only on jira screens.

The problem is that on context field section i see all fields that shoud be there, but they are not shown on JSD view issue customer form.

[Jack Brickey]

got it. I was confused by the use of form which is really associated to creating an issue. You are referring to the view issue screen. Here is an article that references the custom fields available in the portal view screen - list-of-supported-custom-fields-for-request-types-in-jira-service-desk-customer-portals 

[D S]

Sorry for this confusion.
The problem is that my custom field is text field. I am talking about this form customer screen.

I have added fields to all screens. Rechecked everything, field immediately appears in all Jira forms/screens. But JSD screen is empty. 

Issues view Forms have no effect at all.

If i add field to visible form at request form, it appears only as part of request, and only if it is set by client. if it will be hidden it request form, it can't be later be shown in issue view.

I tried different fields types. Maybe field visibility for customers just not available at jsd at all.  

[Jack Brickey]

Please note that the "Request form" you find under project settings > request type > edit is for the "Create" operation not the "view" operations. To have a field appear in the view screen it simply needs to a) be defined on the view screen and b) contain data. So in your test issue do you have something actually in the text field? Below is an example of a text field that appears in the customer's view screen. Also you may see Show details (where "Hide details" is shown below), if so click that.

[D S]

This solution needs to add form to create operation, it will be visible to custromer making it look a bit strange, also change in source data is not so good. And no messages of changes will be send to customers.

So we ended with automation that posts replies in specific format on each field change, to customer. 

Because it seems that there is no normal way to do this, beside the extensions - https://community.atlassian.com/t5/Jira-Service-Desk-questions/Display-Custom-Fields-on-Service-Desk-Customer-Portal/qaq-p/658404

Thank you very much.