Field not available in Forms

[Eddie Harding]

I have a Jira field called 'Affected services' which is a locked field and links to the services we've set up in Jira.

I'm creating a form which will be used for a change request form in JSM but when I try and link a field in the form to this Jira field, it doesn't appear in the list. 

Any ideas? 

It will allow me to add it as a field in the request type but I want it to be in the form so I can take advantage of the forms functionality 

[Simon H · Accepted solution]

@Eddie Harding the Affected Services field is not currently supported within ProForma/Forms. It is something that we are working on. You can track progress of this work here

[Eddie Harding]

Thanks @Simon H , I'll keep an eye on that ticket

[Eddie Harding]

I think I may have found the answer now...

Only certain system fields are supported in Forms at the moment. See final section of this article https://support.atlassian.com/jira-work-management/docs/manage-your-form-fields/  

[Édpo César]

Hi, @Eddie Harding .

This is a common question. First, you need to add your custom field in your project create issue screen.

A tip, click on the link showed in the print bellow, and add your custom field there. After that, you'll be allowed that add your forms.



If my answer helped you, please mark it as accept.

[Eddie Harding]

Hi @Édpo César

Thanks a lot for your help. I have done this and the field is available in the request form section as shown in the screenshot here:

My issue is that I want to create a form using the new Forms feature available in Jira. In there, you can add fields to your form and then link them it to a Jira field (this allows extra functionality such as making fields conditional on the values entered in previous fields) . This has worked for every other field but not for "Affected services". I've highlighted in red where i'm searching for the Jira field but it doesn't find it :(

I have associated the field with all of the contexts and screen that I can but it's still not appearing as an option.

[Scott Bjorke]

Passing along what I learned the hard way...

As much potential as the "Affected Services" (as Services within a Project) offers for JSM, it has one arguably fatal flaw:  Jira will absolutely NOT allow the Affected Services field to appear in either of two logical places:

1. On the customer Portal forms for Request Types that are based on either Incident or Service Request issue types (although it can be shown on Change based Request forms since needed to identify which Service is to be Changed)

2. In Exports to CSV files as human-readable values. Jira reporting and dashboarding leave a lot to be desired, so exporting data to Excel seems pretty inevitable. Here's the hook:  Despite seeing the display name on-screen when a filter is executed, all Export options will omit the display name and instead include only its obfuscated, non-human-readable ID value! You would have to maintain your own XLOOKUP table in Excel to provide the displayable values before proceeding further. We did this for a while until someone created a custom field hidden on forms called "Affected Services Name(s)" and an Automation that populated it from Affected Services any time Affected Services was updated on a record.  Although this worked on-screen and for pushing displayable values into Excel, it also cost us a lot of Automation usage which we discovered too late led to reaching our monthly Automation limit. Ugh -- it's always something.

I read in a couple of places online that JSM might behave this way out of concern for security. Perhaps to prevent anyone with public portal access to see which apps/services/etc a company uses in order to exploit them somehow.  I don't rightly know but it's frustrating nonetheless and requires either add-ons, custom fields, and/or what should otherwise be up to the Client whether to show them or not. Maybe "Assets" or Components offer options but then all aspects of JSM would have to be refactored to use those and we're in too deep with Affected Services to go back any time soon.

Lengthy, sorry, but I hope this helps. Again, IMHO, an arguably fatal flaw within JSM. :(