Problem Definition

      Customers are not able to push Assets Data to Sandbox. Due to that , all Assets custom field data will be broken. On top of that, due to Assets workspace ID different in Sandbox , imported automation with Assets related configuration will be broken. ( separated bug : https://jira.atlassian.com/browse/JSDCLOUD-10256).

      Suggested Solution

      Ability to copy Assets data to Sandbox and remain the same workspace ID in Sandbox.

      Why this is important

      Easy for admin to apply the same Assets data in Sandbox.

      Workaround

      • Take object type export from Production and import it to Assets Sandbox.
      • Update again the Assets custom field configuration ( Reselect the object schema) .
      • Update again the automation configuration (Reselect the object schema)

            [CLOUD-11254] Ability to copy Assets Data to Sandbox

            Hi! 

            Is there any update on this?

            Rafael Melo added a comment - Hi!  Is there any update on this?

            Sam S added a comment - - edited

            I know this request is set to priority but currently not having this ability severely limits our ability to utilize our sandbox environment. It is an urgent need. I know for many users this is essential for testing capabilities in their sandbox. I would like to know why this is something we have to ask for when generally systems allow an exact copy of Production to be pushed into the sandbox.

            Sam S added a comment - - edited I know this request is set to priority but currently not having this ability severely limits our ability to utilize our sandbox environment. It is an urgent need. I know for many users this is essential for testing capabilities in their sandbox. I would like to know why this is something we have to ask for when generally systems allow an exact copy of Production to be pushed into the sandbox.

            This is also very important for our customers. Please add this basic feature to JSM. 

            Klara Bras added a comment - This is also very important for our customers. Please add this basic feature to JSM. 

            What is the last status of this?

            goktug.borlu added a comment - What is the last status of this?

            +1

            Paul Geldert added a comment - +1

            I'd rather have a different WorkspaceID, just to avoid wrong API calls changing PRD.

            But this can be easily done with data promotion config files!

            Fanny Vachet added a comment - I'd rather have a different WorkspaceID, just to avoid wrong API calls changing PRD. But this can be easily done with data promotion config files!

            Same here - very much needed.
            We have a lot of assets and asset custom fields, but our sandbox gets more and more useless for tests as we can't update the data there to a actual state.

            Bernhard G. added a comment - Same here - very much needed. We have a lot of assets and asset custom fields, but our sandbox gets more and more useless for tests as we can't update the data there to a actual state.

            hello Atlassian,

            is there any progress? its been few years, don't you think it is important? Please move it faster ...we need this feature, Asset is growing and this is very much needed !

            Shankar Rishikesh added a comment - hello Atlassian, is there any progress? its been few years, don't you think it is important? Please move it faster ...we need this feature, Asset is growing and this is very much needed !

            +1

            Gaurav Pratik added a comment - +1

            Shenandoah added a comment -

            I have advocated and we have used the assets completely in conjunction with our internal help desk through Jira Service Management. It is a great part of Jira and has allowed us to do a really good job of change management. However, not being able to merge the Assets is detrimental especially given the intent of Assets and the capability. 

            Shenandoah added a comment - I have advocated and we have used the assets completely in conjunction with our internal help desk through Jira Service Management. It is a great part of Jira and has allowed us to do a really good job of change management. However, not being able to merge the Assets is detrimental especially given the intent of Assets and the capability. 

              90325da67d46 Mohamed Hassan
              nroslan Atiqah Roslan
              Votes:
              652 Vote for this issue
              Watchers:
              308 Start watching this issue

                Created:
                Updated: