Empty all fields when cloning issue

[Sander Spoelstra]

Hi,

Within our Jira server (locally hosted) we've got tons of projects. Pretty much every customer and most of the departments have their own project. Not all projects share the same workflows and not all projects share (custom) fields, meaning that project A can have a completely different set of (custom) fields that it uses than project B. Through field configuration (schemes), field context and screen / workflow restricted field occupation, this usually isn't really an issue. 

However, there are some situations in which the fields are copied between the various projects, even if the fields are not applicable within that project. For example:

• We are able to clone++ tickets from one project to another which means that all (custom) fields are copied from one project to another as well
• When exporting tickets with the 'all fields' option, all fields are exported, not just those that are available within the project

Some of the more critical fields like Sprint and some custom fields containing client specific information are emptied actively in post functions in the 'Create' workflow step. However, it is almost impossible to do this for all fields for all different workflows within the scope of projects.

Is there a possibility to actively empty all fields while cloning, leaving only those fields that are availalbe in the new project / filled by the user?

We do have the Scriptrunner addon, but would like to minimalise the amount of script (listeners) we have in place due to server load and performance.