Skip to end of banner
Go to start of banner

Cloning and Import problems

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Exception when trying to create JIRA issue project key

The most common reason for the cloning/import process to fail is related to Jira Field Configuration. 

The "Required" fields must be changed to "Optional" when the App is cloning/importing the program.

Keep in mind the change of the Field Configuration scheme has to be applied to the target Jira project (the project issues get copied to). 

We recommend creating a temporary scheme instead of changing an existing one. This way, other projects will not be affected. Then, when needed, you apply a "temporary" configuration to a project instead of changing an existing configuration (many projects may use that) to minimize the impact.

To make things easier, you may copy an existing configuration:

View-Field-Configurations-partyzant2 (2).png

Name it to make things clear for other users:

Copy-Field-Configuration-partyzant2.png

Click on the field configuration name and change all items to "optional" within it:

View-Field-Configurations-partyzant2 (1).png

Add a new field configuration scheme:

Make sure that the correct field configuration is associated with the scheme:

Go to the Jira project that is added to the Box scope (the project Jira issues will be copied to):

Find the field configuration:

Change the scheme:

You can proceed with the cloning after changing the Field Configuration.

  • No labels