When you copy data from the production site to the sandbox, users and groups are copied separately. For example, a group named jira-software-users-test would be named jira-software-users-test-sandbox-123 in the sandbox.įor the sandbox you want to provide access to users, select Manage access.Īdd people to the appropriate sandbox groups. The group names in your sandbox will be similar to the product group names. After creating a sandbox, only the org admins are given access to the groups. In the production site, the users and groups exist in the organization level, so they don’t need to be copied to the sandbox. We're working on a more streamlined data copy for sandboxes, and we’d appreciate any feedback on what is important to you with data copy to sandboxes. Leave feedback at sandbox environment for cloudĪccess to the sandbox environment is not granted by default, as it is a product testing environment. If you create a new Jira sandbox, and you already have a Jira sandbox linked through the same URL, your new sandbox will create with your production data. This could result in incident links not displaying like they would in production. If you have Jira Software, Jira Work Management, and Jira Service Management sandboxes linked through the same URL, data will copy for all the Jira sandboxes (excluding features powered by Opsgenie) because they are built on the Jira platform. We'll send you an email when it's complete. The larger size of the data being copied over, the longer it will take. It could take up to 2 days for Jira products and 13 days for Confluence to copy data from production into your sandbox. We also disable app links, external email notifications, and integrations with Bitbucket and Slack.
To ensure that your production environment and your users are not impacted, we don’t copy webhooks or OAuth tokens. When you copy new data into a sandbox, users and groups merge with the data you have in the sandbox Product access settings (you’ll need to add users to groups for permissions to apply)Īlthough automation rules aren’t automatically copied into a sandbox, you can manually export and import automation rules Jira Service Management features powered by Opsgenie, (including all content accessed through the Opsgenie URL, as well as alerts and on-call schedules) Space configuration data (including space settings, permissions, and user-created templates) Portal-only accounts for Jira Service Management Project configuration data (including workflows, global permissions, schemes, screens, custom field configuration, issue types, and board configuration) Media files (including media attachments, avatars, and logos) Jira issues and field content (including system and custom fields) ❌ Data that can't be copied into a sandbox Select your organization if you have more than one.
Learn more about admin permissions and groups and product access To create a sandbox, you must have organization admin permissions. To become an organization admin you’ll need to reach out to an existing organization admin. Once created, you can give all admins and users access to sandboxes the same way you do for production environments. You can also create a sandbox if your production Jira Work Management is on a Premium plan. You can create a sandbox if your production Jira Software, Jira Service Management, or Confluence are on Premium or Enterprise plans. If your team would also be interested in having more than one sandbox, let us know through the multiple sandboxes feature request.
JIRA MANAGE APPS SOFTWARE
For example, if you have a Jira Software production environment, you can only create one Jira Software sandbox. Currently, you can only create one sandbox for each linked product.
0 kommentar(er)
