Exception when trying to create JIRA issue project key
.png?version=2&modificationDate=1715261730203&cacheVersion=1&api=v2)
The most common reason for the cloning/import process to fail is related to Jira Field Configuration.
The "Required" fields have to must be changed to "Optional" for the time when the App is cloning 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). .png?version=1&modificationDate=1715261724835&cacheVersion=1&api=v2)
...
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 (that many projects may be in use by multiple different projectsuse that) to minimise minimize the impact.
...
To make things easier, you may copy an existing configuration:.png?version=1&modificationDate=1715261724382&cacheVersion=1&api=v2)
...
Name it to make things clear for other users:
...
Click on the field configuration name and change all items to "optional" within it:.png?version=2&modificationDate=1715261722564&cacheVersion=1&api=v2)
...
Add a new field configuration scheme:
...
Make sure that the correct field configuration is associated with the scheme:
.png?version=2&modificationDate=1715261723146&cacheVersion=1&api=v2)
...
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.