Cloning project configuration will change configuration of project specific fields
Issue #51
resolved
We have a template project having a project specific field.
When we are using project specific fields, we create a configuration for each project using this field to avoid them affect each other when changing values in one project.
But each time we clone the template, all projects will be moved to one configuration leave other configuration's project part blank.
It happened several time. And when projects using one field increases, it is very annoying to make it right each time.
Comments (7)
-
repo owner
-
repo owner
-
assigned issue to
Holger Schimanski
- edited description
-
assigned issue to
-
reporter
It is the first plug-in. Clone project for JIRA. And field type is Project Specific Multi Select Field.
-
reporter
JIRA version is JIRA v6.4.5. Clone plug-in version is 2.0.1. project specific field plug-in version is 2.4.4.
-
repo owner
How does cloning work, when you use JIRA standard multi select field and separate custom fields contexts for each project like you have for Project Specific Multi Select Field?
-
reporter
Hello,
For cloning JIRA standard multi select field, it will not add the cloned project to custom configuration. But the already configured cutom configration will not be moved to default one. It is not the expected perfect performance but it will not change the values of the already exsiting field.
-
repo owner
- edited description
- changed status to resolved
Very old issue never heard again of this problem over year. Closing the issue.
- Log in to comment
You mean clone project via
What custom field type are you using?
What JIRA version and what version of the plugin are you using?
Best regards, Holger