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

When bulk moving a set of objects where a non unique attribute type is mapped to a unique attribute type, will not respect unique requirement after move, in the edge case where the attribute value is not unique within the set of objects being moved

XMLWordPrintable

      Issue Summary

      When bulk moving a set of objects where a non unique attribute type is mapped to a unique attribute type, will not respect unique requirement after move, in the edge case where the attribute value is not unique within the set of objects being moved.

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

      1. Create object type1
      2. Add an integer attribute, and set it to be unique
      3. Create object type2
      4. Add an integer attribute and set it to be NOT unique
      5. Create two objects of type2, ensure that the integer value is set to "2" for both objects
      6. bulk move the 2 objects from type2 to type1, selecting "Validate objects on move option"
      7. Observe that we now have to objects of type1 not respecting the unique rule

      Expected Results

      One of the objects should not move

      Actual Results

      Both objects are transferred to type1 

      Workaround

      Move objects one by one

            [JSDSERVER-15174] When bulk moving a set of objects where a non unique attribute type is mapped to a unique attribute type, will not respect unique requirement after move, in the edge case where the attribute value is not unique within the set of objects being moved

            There are no comments yet on this issue.

              Unassigned Unassigned
              d905be0698b9 Thomas Bowes (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated: