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

improve Assets import logs in relationship to violation of unique constraint

    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      At the moment the Assets import logs print an exception where a unique constraint on an attribute set as unique is violated but they do not print which item value is violating it.

      Ex.

      • an attribute serial number is set as unique
      • the import source try to import a serial number which already exists in another object in the object type
      • following exception is thrown out:
      Error messages: context: rlabs-insight-attribute-5762; messages: [ErrorMessage {i18nKey='rlabs.insight.i18n.constraint.violation.unique', parameters=[Name of the attrribute], additionalMessage=null}
      

      As above example the error report the cause and the attribute name but not the actual value which cannot be duplicated.

      Adding the offending value as well would make a research quite more easier.

          Form Name

            [JSDSERVER-13261] improve Assets import logs in relationship to violation of unique constraint

            Andrew Bui added a comment -

            We're not explicitly logging the attribute value due to conflicts with permissions/hidden attributes, however we will now be logging the object ID and attribute data so the value can be deduced from this information. 

            Andrew Bui added a comment - We're not explicitly logging the attribute value due to conflicts with permissions/hidden attributes, however we will now be logging the object ID and attribute data so the value can be deduced from this information. 

            Hi,
            is there a fix planned?

            I am daily facing an filled error log and it is not possible to find out which object (value of the unique attribute) is causing the issue.

            Christian Solle added a comment - Hi, is there a fix planned? I am daily facing an filled error log and it is not possible to find out which object (value of the unique attribute) is causing the issue.

              f31f2aa3fba9 Andrew Bui
              tmarchionni@atlassian.com Tiziana Marchionni
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: