Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Custom field doesn't copy when cloning a ticket

Nadav Eckstein June 28, 2018

I have two custom fields, both are configured exactly the same way and are exactly the same type. One copied when cloning and the other doesn't.

Both fields have values of course.

Only different I can think of is that one gets its value manually and the other one is copied from another field as a post-function of the create transition.
But I don't understand why this should matter.
It doesn't change anything if I edit the field before cloning.

 Please assist, this is very important.

Thanks, 

Nadav.

2 answers

1 vote
Deleted user June 29, 2018

Hi Nadav,

Is it the same issue type and project? I guess it is, but maybe there is a difference in the schemes configuration (not in view scheme, hidden via field configuration scheme, context...)

Nadav Eckstein July 1, 2018

Hi Cristian,
Thanks for the quick response.

It is the same project and type and I can't see any differences in the configurations of the fields. Like I said, both fields have values and are shown in the view but if I clone the ticket, one is copied to the clone and the other is empty. 

0 votes
Deleted user July 18, 2019

Are both fields available on the create/edit screen?

I seem to be running into a similar issue with a custom field being required at creation time, but not cloned into the new issue. Resulting in a NullpointerException

The only problem I can think of is the recently changed configuration of hiding a required field from the dit screen.

Manually creating one, doesn't give any problems

Suggest an answer

Log in or Sign up to answer