Hi @Nikhil , @Christos Moysiadis
this is sort of an addition to @Christos Moysiadis 's answer.
If the clone goes to another project, which should have different Field Configuration, you can decide what field in which screen should be screened or not, even when the field is added to the screen associated.
Cheers,
Robiert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nikhil ,
as long as i know, hiding a field can be made through the screen section in Jira administration page. The information is global for the issues and i don't thing that this is possible for only one issue.
Now, if the cloned ticket's destination is a project, in which the field is not screened , then this is solved (or not ?)
Best regards
CM
PS: if another member knows something else then i would like to know it too :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Nikhil
Currently, Jira doesn't support cloning an issue into another project. You can "move" the issue in another project and in the destination project you can have the field hidden in the field configuration.
I personally use "Clone plus" plugin for all the cloning operations as out of the box Jira doesn't provide much features when it comes to cloning options.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.