How do I add the Parent field to the request form so it shows in the portal?

[Jack_Marquez]

We would like to utilize our change form on the portal for our internal IT staff to use. Many of our change requests are linked to projects in Jira, so adding this field would make it easier to describe the purpose of the change. However, for some reason, when you add 'Parent' to the request form, it automatically marks it as hidden from the portal. With portals now being secure, we want to move more of our internal forms to the portal for ease of use. 

[Joseph Chung Yin · Accepted solution]

@Jack_Marquez -

What "Parent" field are you referring to?  Are your internal IT Staff use portal to create his/her issues for your JSM project?

Please advise, so we can assist further.

Best, Joseph Chung Yin

[Jack_Marquez]

Hi, I'm referring to the 'Parent' field, which replaced 'Epic' and 'Parent Link' in the agent view. And yes, we want our internal IT Staff to use the portal so that we can use forms that can be inserted with the conditional questions, which can't be done if you create it from the agent view. Does that help explain what we are trying to do. 

[Joseph Chung Yin]

Thanks Jack for the clarification.  It is still my understanding as of right now, this is still not possible to "un-hide" the Parent field...

You may want to create a custom field but it would not be able to validate that the issue key entered is the correct one. Where you need to guide the users to enter the Epic issue key only, for example, XYZ-123.

Then create an automation rule to update the parent field with this value.  This is only a workaround solution.

Finally, you may want to contact Atlassian Support Team to obtain more assistance on using "Parent" field in a JSM env.  (https://support.atlassian.com)

Sorry.

Best, Joseph

[Jack_Marquez]

Hi Joseph, I was afraid you were going to say that it isn't possible. I thought to try the custom field, then use automation to populate it, but if people can't easily look up the epic or enter the epic issue incorrectly, it will not work as expected. 

I will see about opening a ticket with Atlassian to explore the possibility of adding it as a product enhancement later on. I appreciate your assistance with this. 

Thank you, 

Jack