Implications of Using an Attached Form

Question

Hello,

I am looking to change the implementation of the service portal by obtaining information from users through an 'Attached form' rather than users entering information through the default fields.

Using the 'Attached Form' allows for more flexibility in what is asked from customers, however I want to ensure that this does not affect other team members or work flows. For example, I was considering that automation rules, filters, or certain dashboards could potentially be affected.

It appears for one specific project I checked that these should not be affected, however I am considering the bigger picture with this being implemented across multiple projects.

Are there any considerations I should be aware with using an 'Attached Form'? Are there any functionalities known to break when using an 'Attached Form'?

Here is a screenshot of what I have configured:

Thanks!

Christopher Yen · Accepted Answer

Hi @Kalen Peredo

I believe each project has their own set of forms and request types so the impact should be contained within the project the form is added/used.

When we switched from request type fields to using Forms we did have to train our users to expand the form to see the fields, with forms supporting conditional sections/fields there would be a lot of empty fields if we put them all in the issue view so we just keep the request form expanded to work out of. Other than that the transition was smooth