How can certain JIRA fields be restricted from cloning?

[Trevor Samaroo]

I'd like to mark some fields as 'not cloneable'. is that possible? (without customizing the cloning operation code myself)

Thanks!

[Sandor Krisztian Andre]

It's doable with scriptrunner custom postfunction :)

[Satya Boddu]

could you give details on how to do it

[Rakesh Kande]

can you please let me know if there is a solution for this

[Nic Brough -Adaptavist-]

No, nothing new, other than "write your own clone function"

[Karl Shlayfman]

did you ever figure out a way to accomplish this?

[Karl Shlayfman]

could you please provide some more info on this. I am also in need to be able to blank fix version when cloning an issue. I see that someone said there is an option of not cloneable whithin field configuration but I can not find it? any help would be really appreciated.

[Cyril Egan]

If you have the Jira Suite Utilities plugin....

1. Edit the workflow.
2. Click on the first step in the workflow.
3. In the "Workflow Browser" section click "Create Issue" transition.
4. Add a post function to "Clear Field Value" for each custom field you don't want to clone.
5. Publish the workflow and try it out.

When you do a Clone it will fire the "Create Issue" transition on the cloned issue and run the new post functions clearing them out. No history will be recorded on the cloned issue showing the fields were cleared out.

[Nic Brough -Adaptavist-]

Note that this also clears out fields if the users enter them when creating a new issue in that project, so it's only appropriate for fields that you don't want to use on the creation on a new issue.

[Nic Brough -Adaptavist-]

Yup, but that's coding in the core of Jira...

[Trevor Samaroo]

A clean approach would be to add "not cloneable' to the feild configuration options.

btw, my use case is that i record certain control action, like 'approve', by putting the actioner's name in a field during a workflow post function execution. so cloning clones these audit fields, which is a problem.