Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-10000

Ability to move objects to another object type within object schema in Assets

    • 914
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    • Hide

      Hello!

      This is a feature we are sure we want to address as a part of our roadmap for Assets. Unfortunately it has not yet been scheduled as a number of other important features are being addressed first. I'll provide more updates as this changes. 

      All the best,

      Justin King
      Product Manager, Jira Service Management.

      Show
      Hello! This is a feature we are sure we want to address as a part of our roadmap for Assets. Unfortunately it has not yet been scheduled as a number of other important features are being addressed first. I'll provide more updates as this changes.  All the best, Justin King Product Manager, Jira Service Management.

      Currently, for Server/Data Center, we have an option to move one or more objects from one object type to another within the same object schema: Move Objects

      This function helps to enable/disable inheritance using: https://www.youtube.com/watch?v=mPLTfsIJyVg

      However, this function is not available in the Assets on Cloud.

       

      Alternatives

      Workaround 1
      The objects can be exported from object type 1 and then imported into object type 2:
      Export objects
      Import objects

      Workaround 2
      Bulk clone objects to a different object type or schema using an Automation rule:
      How to bulk clone objects to a different object type or schema using Automation for Assets

       

          Form Name

            [JSDCLOUD-10000] Ability to move objects to another object type within object schema in Assets

            How is this not possible yet? This is a basic feature that is needed immediately. This was available on our on-premise solution (back when it was owned by Riada) and we used this quite frequently in the past. Incredibly disappointed that this has not been implemented. 

            Joseph Orellana added a comment - How is this not possible yet? This is a basic feature that is needed immediately. This was available on our on-premise solution (back when it was owned by Riada) and we used this quite frequently in the past. Incredibly disappointed that this has not been implemented. 

            Hello! We desperately need this. Please please please upgrade the priority and schedule it. It has been sorely missing since 2023 when we moved to Cloud. Jira Insight used to have this and it was a HUGE part of being able to have our inventory work smoothly. 

            Brigid Abreu added a comment - Hello! We desperately need this. Please please please upgrade the priority and schedule it. It has been sorely missing since 2023 when we moved to Cloud. Jira Insight used to have this and it was a HUGE part of being able to have our inventory work smoothly. 

            This is so basic, it needs to happen asap. Assets is still just a side project with limited use at this point. 

            Cosmo Denger added a comment - This is so basic, it needs to happen asap. Assets is still just a side project with limited use at this point. 

            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?

            Dear Atlassian-Team

            A flexible CMDB is nowadays an important component of modern IT Service Management.

            If Jira Service Management wants to remain competitive, this feature should be integrated as a standard function, as it was in the past with the on-premises version.

            Best regards,

            Roman

            Roman Muchenberger added a comment - Dear Atlassian-Team A flexible CMDB is nowadays an important component of modern IT Service Management. If Jira Service Management wants to remain competitive, this feature should be integrated as a standard function, as it was in the past with the on-premises version. Best regards, Roman

            Hello Team,

            Here yet another use case why this is so critical to have:

            • You build a nice CMDB where a user is an object
            • Different Object Types link to the users
            • Now you switch and/or use an asset importer to maintain the list of users
            • --> You need to redo all of those links, because export/import will not retain the incoming links

            Furthermore, it is common that a CMDB evolves and things get moved around and consolidated.

            Andreas Krupp added a comment - Hello Team, Here yet another use case why this is so critical to have: You build a nice CMDB where a user is an object Different Object Types link to the users Now you switch and/or use an asset importer to maintain the list of users --> You need to redo all of those links, because export/import will not retain the incoming links Furthermore, it is common that a CMDB evolves and things get moved around and consolidated.

            Hi Atlassian,

            This is blocking one of the most requested features for our Shoppie app, and it’s quite difficult to believe that this functionality is not available. Many of our customers have been requesting this feature. Could you provide any feedback or a timeline for its availability?

            Best regards,
            Marin, CEO Caelor

            Marin Varvodic added a comment - Hi Atlassian, This is blocking one of the most requested features for our Shoppie app, and it’s quite difficult to believe that this functionality is not available. Many of our customers have been requesting this feature. Could you provide any feedback or a timeline for its availability? Best regards, Marin, CEO Caelor

            Between this and JSDCLOUD-10975 I am struggling to justify paying for Jira Service Premium. The Assets feature is just not mature enough for the price tag. 

            Hercules Konstantopoulos added a comment - Between this and JSDCLOUD-10975 I am struggling to justify paying for Jira Service Premium. The Assets feature is just not mature enough for the price tag. 

            I pledge you cannot name it "Assets" if that functionality is not given.

            Konstantin Weber - SVA added a comment - I pledge you cannot name it "Assets" if that functionality is not given.

            Do the workarounds cover the scenario where you have linked objects with 1:1 cardinality?

            Justin Deutsch added a comment - Do the workarounds cover the scenario where you have linked objects with 1:1 cardinality?

              7260236ab89d Justin King
              asantos2@atlassian.com Augusto Pasqualotto (Inactive)
              Votes:
              341 Vote for this issue
              Watchers:
              184 Start watching this issue

                Created:
                Updated: