Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Custom field doesn't copy when cloning a ticket

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.



2 answers

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...)

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. 

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
Community showcase
Published in Marketplace Apps & Integrations

Jira issue check and more advanced commit verifications for Bitbucket DC

Pre-receive hooks that verify the Git commit message, the modified files, and implement similar code change controls used to be requirements of large enterprises working in regulated industries only....

19 views 0 0
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you