Issue Summary

      If in the Parent site there's an external directory managing the users besides the Jira internal, the users will not be imported to Sandbox and the copy process will fail. 

      Steps to Reproduce

      1. Integrate any External directory to manage the users, e.g. Crowd, AD in Jira
      2. Add users to this external directory and they will be properly created in Jira and they're associated with this external directory.
      3. Start the copy data process to Sandbox.

      Expected Results

      The users from both the internal and external directories would be imported into Cloud.

      Actual Results

      The copy process fails and this error is shown in SBAS:

      "ValidationProgress(status=FAILED, rawProgress=100, subtask=null, message=, errors=[We have detected users from external directories. <a href="https://confluence.atlassian.com/jirakb/migrating-from-external-directory-to-jira-internal-user-directory-968659306.html" target="_blank">Convert your external directory to internal ones on server</a>, take a fresh backup, import again. <a href="https://confluence.atlassian.com/cloud/determine-your-user-migration-strategy-991930388.html" target="_blank">Learn more</a>.])"

      Workaround

      Migrate the users from the external directory to the internal directory in the Parent instance prior to copying data.

            [CLOUD-11482] Support users managed by an external directory in Jira during Sandbox Data Copy

            Matthew Hunter made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Matthew Hunter made changes -
            Labels New: timeout-suggestion-bulk-close

            Atlassian Update - July 18, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - July 18, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!
            Andy Heinzer made changes -
            Component/s New: Admin - Sandbox - Data copy [ 66419 ]
            Greice Faustino (Inactive) made changes -
            Summary Original: Support users managed by an external directory in Jira would during Sandbox Data Copy New: Support users managed by an external directory in Jira during Sandbox Data Copy
            Greice Faustino (Inactive) made changes -
            Summary Original: It would be great if users managed by an external directory in Jira would be imported during Sandbox Data Copy New: Support users managed by an external directory in Jira would during Sandbox Data Copy
            Greice Faustino (Inactive) made changes -
            Description Original: h3. Issue Summary

            If in the Parent site there's an external directory managing the users besides the Jira internal, the users will not be imported to Sandbox and the copy process will fail. 
            h3. Steps to Reproduce
             # Integrate any External directory to manage the users, e.g. Crowd, AD in Jira
             # Add users to this external directory and they will be properly created in Jira and they're associated with this external directory.
             # Start the copy data process to Sandbox.

            h3. Expected Results

            The users from both the internal and external directories would be imported into Cloud.
            h3. Actual Results

            The copy process fails and this error is shown in SBAS:
            "ValidationProgress(status=FAILED, rawProgress=100, subtask=null, message=, errors=[We have detected users from external directories. <a href="https://confluence.atlassian.com/jirakb/migrating-from-external-directory-to-jira-internal-user-directory-968659306.html" target="_blank">Convert your external directory to internal ones on server</a>, take a fresh backup, import again. <a href="https://confluence.atlassian.com/cloud/determine-your-user-migration-strategy-991930388.html" target="_blank">Learn more</a>.])"
            h3. Workaround

            Migrate the users from the external directory to the internal directory in the Parent instance prior to copying data.
            New: h3. Issue Summary

            If in the Parent site there's an external directory managing the users besides the Jira internal, the users will not be imported to Sandbox and the copy process will fail. 
            h3. Steps to Reproduce
             # Integrate any External directory to manage the users, e.g. Crowd, AD in Jira
             # Add users to this external directory and they will be properly created in Jira and they're associated with this external directory.
             # Start the copy data process to Sandbox.

            h3. Expected Results

            The users from both the internal and external directories would be imported into Cloud.
            h3. Actual Results

            The copy process fails and this error is shown in SBAS:
            {code}"ValidationProgress(status=FAILED, rawProgress=100, subtask=null, message=, errors=[We have detected users from external directories. <a href="https://confluence.atlassian.com/jirakb/migrating-from-external-directory-to-jira-internal-user-directory-968659306.html" target="_blank">Convert your external directory to internal ones on server</a>, take a fresh backup, import again. <a href="https://confluence.atlassian.com/cloud/determine-your-user-migration-strategy-991930388.html" target="_blank">Learn more</a>.])"{code}
            h3. Workaround

            Migrate the users from the external directory to the internal directory in the Parent instance prior to copying data.
            Greice Faustino (Inactive) created issue -

              Unassigned Unassigned
              44981f7279ac Greice Faustino (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: