This documentation has moved. For the most recent documentation, check out https://docs.adaptavist.com. Please update your bookmarks and links.
There are some differences between JIRA 7 and 6 in the configuration items managed by Project Configurator. The plugin is prepared to take a configuration exported from JIRA 6 and adapt it to JIRA 7, as this is considered a likely use case. If you need to move your configurations in the reverse direction follow these steps.
DowngradeXMLConfigFilesFromJ7ToJ6.xslt
java -cp saxon9he.jar net.sf.saxon.Transform J7-file.xml DowngradeXMLConfigFilesFromJ7ToJ6.xslt > J6-file.xml
4. The transformed XML file created in step 3 can be imported into a JIRA 6 instance.
Removed items
Remember that there are a few configuration elements in JIRA 7 that do not exist in JIRA 6. The transformation described above will remove all those elements from the configuration file so that it can be imported into JIRA 6. These elements are:
The transformation file is designed to display a message when any of these elements are removed from the configuration. This should help you to assess the possible impact of these changes. The messages would be like:
Removing permission SERVICEDESK_AGENT granted to holder "Service Desk Team" in scheme Default software scheme Removing permission TRANSITION_ISSUES granted to applicationRole "ANY" in scheme Default software scheme Removing permission VIEW_DEV_TOOLS granted to applicationRole "ANY" in scheme Default software scheme Removing permission VIEW_READONLY_WORKFLOW granted to applicationRole "ANY" in scheme Default software scheme Removing permission VIEW_VOTERS_AND_WATCHERS granted to applicationRole "ANY" in scheme Default software scheme Removing permission WORK_ON_ISSUES granted to applicationRole "ANY" in scheme Default software scheme Removing gadget identified by module key com.atlassian.jira.gadgets:introduction-dashboard-item in dashboard Shared with project Removing type element for project SEJIC