Default Configuration Question, Project Configurator plugin

Hi,

We are trying to export a whole instance to another instance, and came across this issue. We are unable to rename the Default Field Configuration and Default Workflow scheme.  

what is the impact when we export all projects (whole instance) to another instance. Does it over write the target instance's Default schemes? 

could you please suggest us steps, not to overwrite the default schemes in the target instance.
Note: The default schemes in both instances are Different.

 please let us know about this.

Thanks in advance

Harish. 

1 answer

Hi Harish,

Yes, that would overwrite the target instance's schemes.

I assume you want to import projects from the source instance with the same schemes they had at the source. Then you would have to act this way.

Workflow schemes

  • First of all, bear in mind that if you export workflows from source that have the same name as workflows in target, these will be overwritten. In order to avoid this problem workflows with names already taken in the target will have to be renamed too.
  • Default Workflow Scheme: AFAIK this means using the default JIRA workflow (which cannot be edited) for all issue types, so I do not understand how that could be different in the target and source instances. Nevertheless, let us suppose the source projects are using a workflow scheme with a name that is already in use by another workflow scheme in the target.

  • Steps
  1. Export configuration for all projects.

  2. We have to detect which workflows will overwrite corresponding objects in the target. The easiest way to find out is running a simulated import into the target of the XML file exported in step 1. The load trace will tell you when an existing workflow is being modified or a new one is created. Note down the name of all the workflows that will be modified.

  3. Go to the source instance. Create copies with a different name of all the workflows in the list created in step 1.
  4. Review all active workflow schemes. When they use one of the renamed workflows, change it so that the scheme now uses for the same issue types the recently created copy of the workflow (with the new name). Issue migration should be straightforward (no issue must be assigned to a new status) because the new workflows are exact copies of the old ones.
  5. Repeat steps 1 and 2. This time note down the name of all workflow schemes that would be modified. (By the way, the simulation should not show any workflow being modified now in the target)
  6. Go to the source instance. Create copies with a different name of all the workflow schemes in the list created in step 5.
  7. Review the projects. When they use one of the renamed workflow schemes, replace them with the corresponding copy with the new name. The same consideration about issue migration applies here than in step 4.
  8. (Optional) Steps 3, 4, 6 and 7 will leave a lot of inactive workflows and schemes (all those that have been renamed). Remove them if you want to keep the source instance "clean and tidy" (always a good idea if it is going to be kept alive).

Default field configuration

  • In this case everything is easier, as there is only one object involved. In the general case of field configuration schemes that have the same name as schemes in the target, the process is exactly the same as in the 6 steps above. Just change "field configuration scheme" where it says "workflow scheme" and "field configuration" where it says "workflow"
  • Having to deal only with the Default Field Configuration (you already know that would be modified in the target) allows the process to be simplified to:
  1. In the source instance copy the default field configuration. Give the copy a new name (for example "Source default field configuration").
  2. Create a new field configuration scheme that uses the new "Source default field configuration" as field configuration for all issue types.
  3. Assign the previous scheme to all projects that are using the Default Field Configuration.
  4. Look for other field configuration schemes that use the Default Field Configuration. Change them, replacing that reference with a reference to the new "Source default field configuration".

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 3 hours ago in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

13 views 0 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you