Exporting configuration for changed projects from staging

Still need help?

The Atlassian Community is here for you.

Ask the community

When all the configuration changes are ready in staging, you can promote them to production. The first step is exporting them from staging.

Starting the export

  1. In the staging instance, open a JIRA session as a user with the system administrator permission.
  2. In the top-right corner, open the Administration menu, and click Add-ons.
  3. In the menu on the left, in the PROJECT CONFIGURATOR section, click Export selected projects.

  4. Select the projects that you want to export (to select more than one, use the CTRL key in Windows, or COMMAND key in macOS.)
  5. Select Configuration only below the list of projects, and click Next.

Export options

On the next page, you can fine tune some export options. The meaning of each option is explained on this page. Let's review them and see which are usually the best choice.

  • Filtering custom fields – In most cases, you will export only the custom fields that are used by the exported projects. Exporting all custom fields would add unnecessary complexity to the process. This option is kept mostly for historical reasons and backward compatibility.
  • User export options and Group export options – The choice here depends to a great extent on the management model in place for users and groups, and their part in the changes that have been performed in staging. 
    • Full export – Choose if users and groups are managed in the JIRA internal directory, and have been created or changed in staging.
    • Do not export – Choose if users and groups are managed in an external directory (Active Directory, any other kind of LDAP, etc.), or have not been changed in staging.
    • Do not export and Ignore invalid users/groups – These might be useful when you have a large number of users and groups, and some of them might be inconsistent, e.g. there are references to users and groups that do not exist any longer, or have invalid email addresses.

Bear also in mind that if the production instance has several directories for users and groups, any new user/group will be created in the first writable directory (see here for more details.)

Exporting filters, dashboards, and Agile boards

If the changes developed in staging are centered on a small group of projects, you can export only filters, dashboards, and Agile boards that are related to these projects. In such a case:

  • For filters and dashboards, select the Shared with exported projects option.
  • For Scrum and Kanban boards, select the Associated to exported projects option.

The criteria to decide when one of these objects is shared or associated with a project are these:

Filters and dashboards – They are shared with the project or any of its roles. 

Scrum and Kanban boards – The board appears under the project title at the project navigation menu. This happens when the main filter for the board includes a clause like "project=XXX" that restricts its issues to that project.

Launching the export

Finally, click Export project configuration, and you will navigate to a page with a progress bar that represents the progress of the export task. When the export is completed, your browser will download an XML file with the configuration for the selected projects. Store the downloaded XML file at a known location. 

 

 

 

💡 Let us know what you think

Feedback

Last modified on Mar 26, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.