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

Ability to copy and move objects to a different object type or a different object schema

XMLWordPrintable

    • 25
    • 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.

      Issue Summary

      • Currently, in the Jira Service Management Assets tool, it is not possible to move objects to a different object type or a different object schema, and the Clone action can only create objects in the same object type as the original.

      Workaround

      Suggestion

      • This suggestion propose Atlassian Developers to build this functionality in Assets, in order for Assets to have the ability to copy and move objects to a different object type or a different object schema

          Form Name

            [JSDSERVER-12560] Ability to copy and move objects to a different object type or a different object schema

            EP added a comment -

            +1

            EP added a comment - +1

            Tobias Bosshard added a comment -

            Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

            Tobias Bosshard added a comment - Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

            Paul Ceronio added a comment -

            +1 Need this URGENTLY!

            Paul Ceronio added a comment - +1 Need this URGENTLY!

            Tobias Bosshard added a comment -

            +1

            Tobias Bosshard added a comment - +1

            Niharika Sarabu added a comment -

            The Workaround mentioned in the "Description" is not at all matching to the requirement.

            The requirement is to be able to move the objectTypes along with objects from one schema to another( which is already existing with some different set of objectTypes). Here in workaround you are suggesting to get the new schema with similar set object Types.

            As most of the times, we might realise that an object Type is more relevant with a different schema, and it is not possible to move the objects around

            If we create a new Object Type in the different schema with similar attributes, we will loose the history, references & connected tickets information from the current objects)

            Looking forward for a best possible solution.

            Also let me know if there is a workaround to do this already.

            Niharika Sarabu added a comment - The Workaround mentioned in the "Description" is not at all matching to the requirement. The requirement is to be able to move the objectTypes along with objects from one schema to another( which is already existing with some different set of objectTypes). Here in workaround you are suggesting to get the new schema with similar set object Types. As most of the times, we might realise that an object Type is more relevant with a different schema, and it is not possible to move the objects around If we create a new Object Type in the different schema with similar attributes, we will loose the history, references & connected tickets information from the current objects) Looking forward for a best possible solution. Also let me know if there is a workaround to do this already.

              Unassigned Unassigned
              c3678a055509 Leonardo Souto
              Votes:
              101 Vote for this issue
              Watchers:
              44 Start watching this issue

                Created:
                Updated: