Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-268

Service Desk creates a new Customer Request Type field (vp-origin) every time it starts

      With the right mix of third-party plugin interactions, a customer was able to coax ServiceDesk into inadvertently creating a new Customer Request Type every time JIRA restarted. We're requesting code hardening against this event (presumably a race condition).

          Form Name

            [JSDSERVER-268] Service Desk creates a new Customer Request Type field (vp-origin) every time it starts

            I guess the problem has been resolved but I am wondering the same thing as Mark, is it safe to delete the additional fields and if so, which ones? We have a total of 29 "Customer Request Type"-fields in a JIRA, out of which one is marked as "Locked". I guess this is the one that should be left and that the others could be removed. Safe to do?

            Kristofer Hansson Aspman [Riada] added a comment - I guess the problem has been resolved but I am wondering the same thing as Mark, is it safe to delete the additional fields and if so, which ones? We have a total of 29 "Customer Request Type"-fields in a JIRA, out of which one is marked as "Locked". I guess this is the one that should be left and that the others could be removed. Safe to do?

            Mark Love added a comment -

            We've got the same problem here - I've got 12 identical "Customer Request Type" custom fields, that all seemingly have identical data.

            Is it safe for me to delete 11 of them, and if so which 11?

            Mark Love added a comment - We've got the same problem here - I've got 12 identical "Customer Request Type" custom fields, that all seemingly have identical data. Is it safe for me to delete 11 of them, and if so which 11?

            MattS added a comment -

            Seems more like a Major bug to me!

            MattS added a comment - Seems more like a Major bug to me!

            Philipp Klauser added a comment - - edited

            Found a solution: Do NEVER start JIRA 6.1 with SD 1.1.1.
            This will create more and more "Customer Request Type" custom fields....!
            During JIRA Upgrade (5.2.x to 6.1.x) DEACTIVATE SD, after the Upgrade to 6.1.x immediately upgrade SD to 1.2.4 before enabling SD again.
            Finally test if SD doesn't create new custom fields by disabling/enabling SD multiple times.
            If you still see just one "Customer Request Type" field, everything went well.

            Philipp Klauser added a comment - - edited Found a solution: Do NEVER start JIRA 6.1 with SD 1.1.1. This will create more and more "Customer Request Type" custom fields....! During JIRA Upgrade (5.2.x to 6.1.x) DEACTIVATE SD, after the Upgrade to 6.1.x immediately upgrade SD to 1.2.4 before enabling SD again. Finally test if SD doesn't create new custom fields by disabling/enabling SD multiple times. If you still see just one "Customer Request Type" field, everything went well.

            We have quite a lot plugins installed and need everyone of them.
            Never the less I made the try and

            • Enabled safe mode (all plugins disabled)
            • Activated Service Desk
              -> no more additional customfields were created
              -> But the creation of new request still fails

            Philipp Klauser added a comment - We have quite a lot plugins installed and need everyone of them. Never the less I made the try and Enabled safe mode (all plugins disabled) Activated Service Desk -> no more additional customfields were created -> But the creation of new request still fails

            Problem persists: JIRA 6.1.7 with SD 1.1.1 has this effect too.
            I'll need now a quick fix / workaround because your productive JIRA instance is now affected and I see no way to avoid this behaviour!

            Philipp Klauser added a comment - Problem persists: JIRA 6.1.7 with SD 1.1.1 has this effect too. I'll need now a quick fix / workaround because your productive JIRA instance is now affected and I see no way to avoid this behaviour!

            Philipp Klauser added a comment - - edited

            And as well JIRA 6.1.7 with SD 1.2.1, I will now downgrade to SD 1.1.1

            Philipp Klauser added a comment - - edited And as well JIRA 6.1.7 with SD 1.2.1, I will now downgrade to SD 1.1.1

            Philipp Klauser added a comment - - edited

            exactly the same here, have now 5 "customer request type" fields, lost all request under "my requests", guess SD always swiches to the newest custom field and doesn't find any existing issue having a value stored there...

            Weird and very annoying, pls fix this as soon as possible!

            JIRA 6.1.7 with SD 1.2.4

            Philipp Klauser added a comment - - edited exactly the same here, have now 5 "customer request type" fields, lost all request under "my requests", guess SD always swiches to the newest custom field and doesn't find any existing issue having a value stored there... Weird and very annoying, pls fix this as soon as possible! JIRA 6.1.7 with SD 1.2.4

              Unassigned Unassigned
              jgarcia John Garcia (Inactive)
              Affected customers:
              5 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: