Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-11264

Trashed custom field in Production become Active in Sandbox after Data Copy from Production to Sandbox

      Issue Summary

      The customer is experiencing an unexpected behavior while refreshing their sandbox with production data, the custom fields are not being refreshed in the sandbox.

      "when I viewed in Sandbox the custom fields, I found that there are still custom fields previously created in Sandbox that remained despite the refresh."

      Steps to Reproduce

      • Create a Sandbox
      • Create a custom field in the production instance and Move it to the trash
      • Copy data from production to sandbox
      • Then, the custom field that was moved to the trash on the production instance will appear as active on the sandbox instance.

      Expected Results

      After the copy data from production, the sandbox should have the same data as the production instance, which means that if a custom field was moved to the trash in production it should appear as moved to the trash in the sandbox.

      Actual Results

      The custom field that was moved to the trash on the production instance appears as active on the sandbox instance.

      Workaround

      Permanently delete the trashed custom field in the production instance or even in the sandbox instance, if the copy from production was already done.

        1. screenshot-1.png
          screenshot-1.png
          328 kB
        2. screenshot-2.png
          screenshot-2.png
          314 kB

            [CLOUD-11264] Trashed custom field in Production become Active in Sandbox after Data Copy from Production to Sandbox

            Atlassian!!! πŸ˜”

            This is pretty annoying. You want us to use Jira as an enterprise wide application, and we do. It's a critical part of so many work streams. It's a big and complicated environment with more moving parts than 1 person can manage. 

            With most critical and complicated work environments you make changes in a sandbox and then push those changes up into staging, and then production. Basic best practice. And we're trying so hard to implement that in our organization but then there's these basic functionality issues that really impede the process. We've already got to supplement the process using 3rd party tools, can we please get the basics right and not duplicate deleted things back out of the trash. 

            Thank you πŸ™ƒ

            Jordan McCombs added a comment - Atlassian!!! πŸ˜” This is pretty annoying. You want us to use Jira as an enterprise wide application , and we do. It's a critical part of so many work streams. It's a big and complicated environment with more moving parts than 1 person can manage.  With most critical and complicated work environments you make changes in a sandbox and then push those changes up into staging, and then production. Basic best practice. And we're trying so hard to implement that in our organization but then there's these basic functionality issues that really impede the process. We've already got to supplement the process using 3rd party tools, can we please get the basics right and not duplicate deleted things back out of the trash.  Thank you πŸ™ƒ

            KC Wong added a comment - - edited

            Just take a look at this one: https://jira.atlassian.com/browse/CLOUD-11498

            We all are getting it wrong. The actual purpose of the copy to sandbox is to wipe your sandbox data and copy half of it over. It is by design to be frigging useless. Reviving your deleted custom fields is just the tiny cherry on top.

            KC Wong added a comment - - edited Just take a look at this one: https://jira.atlassian.com/browse/CLOUD-11498 We all are getting it wrong. The actual purpose of the copy to sandbox is to wipe your sandbox data and copy half of it over. It is by design to be frigging useless. Reviving your deleted custom fields is just the tiny cherry on top.

            I was about to create a ticket with Atlassian Support in this regard, but it was deflected by Service Management's Knowledge Base on offering this issue.

            So, consider a +1 on the Support reference count ** custom field. Thanks!

            Ignacio Pulgar added a comment - I was about to create a ticket with Atlassian Support in this regard, but it was deflected by Service Management's Knowledge Base on offering this issue. So, consider a +1 on the  Support reference count  ** custom field. Thanks!

              sperez@atlassian.com santiago
              0a4d3986ddf5 Marcelo Beloni (Inactive)
              Affected customers:
              19 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated: