nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Process type lost connection to assigned fields

spaks

I hope I can explain the problem in an understandble way.. I created a couple of request forms for a certain amount of project. In one case there it is not possible to edit the form, because the relation / connection to the assigend fields is lost. When I click on "add field" nothing happens and the overview gives me the following information:

This request form is linked to the following process type: Bug (9 used by NaN field (s))

Normally I can see the amount of fields assigned to this type, but here I read NaN, which - in my opinion - means, the system has lost control somehow over the assigend fields.

Does someone understand this problem and - in best case - has a solution for me? I am desperate after one hour of trial and error..

Many thanks in advance.

Kind regards

Volker

Accepted answers

Brant Schroeder

@spaks

Can you please share some screenshots of the issue? Are these just standard Jira service request forms created in the application? What fields are the issue? Do they still exist on the instance? Are they still associated with your project?

With the limited information that I have I would suggest doing the following:

Work with the Jira administrator to ensure that the fields causing the issue still exist and were not deleted.
If the field exists make sure that it is associated with the service desk project that is giving you errors.

All comments

Brant Schroeder

@spaks

With the limited information that I have I would suggest doing the following:

Work with the Jira administrator to ensure that the fields causing the issue still exist and were not deleted.
If the field exists make sure that it is associated with the service desk project that is giving you errors.

spaks

Hi Brant,

thanks for your reply. I had lost track on this issue over the christmas time. Lookin at it again we found a surpriding solution. The required fild was not listed. But using the search function it could be found and the amount of usable fields rised fro 13 to 14. Do not know if this is a frontend /cache issue.

But anyway it is solved now, customer is happy.

Thx again, stay safe and have a good time

Regards

Volker

Brant Schroeder

@spaks Can you mark this issue as accepted so others can find this answer, thanks.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk-server

jira-service-management

jira-service-management-server