Risks in moving Request type fields to FORM.

[Vera Valshonok]

Hi Community! 

1. Currently in a Jira project we are using request types without Forms, in order to be able to do branching in the future we want to move all the fields to forms.

Project is active and tickets are a opened all the time.

What could be the risks of moving to forms?Can we loose some info in already created tickets when moving to forms?

Maybe I can read about it somewhere?

2. How Can I set two different requests type under one Request section in portal? 

for example in Portal: request one and after clicking it a person can open request one or request two ( both have different forms and workflows)

Thanks!

[Jeramy · Accepted solution]

@Vera Valshonok - Welcome to the community.

1. Currently in a Jira project we are using request types without Forms, in order to be able to do branching in the future we want to move all the fields to forms.

Project is active and tickets are a opened all the time.

What could be the risks of moving to forms?Can we loose some info in already created tickets when moving to forms?

Maybe I can read about it somewhere?

We use Data Center, so I'm not very familiar with forms. However, I found a few Atlassian topics that might help.

• https://support.atlassian.com/jira-service-management-cloud/docs/what-are-forms/
• https://support.atlassian.com/jira-service-management-cloud/docs/use-forms-in-jira-service-management/

2. How Can I set two different requests type under one Request section in portal? 

for example in Portal: request one and after clicking it a person can open request one or request two ( both have different forms and workflows)

Do you mean something like this?