Error when saving form for a request type

[trthomas]

I have my request type created and am working on my form.  When I attach the form to the request type and try to save the form, I get this message "There are duplicate fields on one of your request types".  Have verified 3 times that there are no duplicate fields.  I even created a new request type, added only 1 field to it, attached the request type to the form, and tried to save the form.  I get the same error message.  

I created the initial request type and form a few months ago.  no problems then.  I needed to update some field names on the form today and this is when the error is happening.  I don't know what to do.  Does anyone have any suggestions or thoughts on this error?

[Guy West]

Any updates here? I am having the same issue as @trthomas . I went to make changes to a request type I had made a few months ago. When trying to save the changes I was met with the same error message:

There are duplicate fields on one of your request types
To avoid fields appearing twice, the ‘Change risk’ Jira field will be removed from the ‘Request a change’ request type so it can be linked in this form.

How was I able to have a field in the request type and linked in the form in the first place if there is a no duplicate fields rule? 

Was there an update released in this space that I missed?

For now I can't make any changes to the request type or the form, as saving it will remove one of the duplicate fields. 

[Joseph Chung Yin]

@trthomas -

Have you check your FORM's configuration elements to see if there are fields where you have mapped it to an issue field for your JSM project incorrectly.  Or, having multiple FORM's elements mapped to the same issue field?

Lastly, If your FORM's elements are properly mapped to issue fields for your request type, you need to also make sure that you don't include the same field in your request type's "Request form" tab.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[trthomas]

@Joseph Chung Yin 

I was able to figure it out.  I needed to rename some fields, due to business policy changes.  This is what caused the issues.  I deleted the custom fields and created new ones.  I was then able to properly set up the form and attach the request type to it.  

Lesson learned.  Don't change custom field names when used in a form.  

[trthomas]

Well nevermind.  I apparently I was just a little too quick to assume I had the answer.  Back to the drawing board and I'll definitely be looking over what you've provided @Joseph Chung Yin 

[trthomas]

Here is my request type:

Here is the form that I have set up.  It shows that the first form field is linked to the request type field. 

Here are the form setting page

Here is the error that I'm getting when clicking Save.

@Joseph Chung Yin what am I doing wrong?  I've set up several forms this way, with no problem, but that was a few months ago.  Was there a JSM update that modified the way forms and request types work together?

[Joseph Chung Yin]

@trthomas -

Keep in mind that to proper map FORM's element to your issue's custom field in your FORM configuration design.

Best, Joseph

[trthomas]

@Joseph Chung Yin 

I apologize, but I don't understand what you are telling me.  Would you perhaps be able to post a screenshot showing me what configuration design I'm supposed to be setting up?  

[Joseph Chung Yin]

@trthomas -

Here you go:

Open your FORM configuration - Using the Build tab on mapping an element to an actual Jira issue field

Here is link in the FORMs documentation on how to link element (form field) to an actual issue field used in your JSM issue - https://support.atlassian.com/jira-service-management-cloud/docs/link-a-form-field-to-a-jira-field/

Hope this helps.

Best, Joseph

[Zvonimir Pavić]

I'm having the same issue here. On one project it is working as it should, on the other one it doesn't work.

It says: "To avoid duplicate fields appearing twice, the ‘URL‘ linked Jira field will be removed from ..." even though the linked field is the same as the one added to view.