Make Clone Issue Configurable

Problem Definition

We would like to disable or limit the use of the "Clone" issue in JIRA. The problem is that the cloning issues makes our issues less manageable. It would carry over too much information from the old issue such as assignee, due dates, fix versions, sprint, etc. while the new cloned issue hasn't been worked on. What the user really wants to do is just copy over the summary, description, etc.

Suggested Solution

Simpler way: just the ability to disable "Clone" function, either globally, or based on users, groups, or project role.

Alternatively, allow us to specify which fields will be included/excluded when copying over information from the cloned issue to the new issue.