We created a custom field recently to identify Change Request categories. The custom field appears, when I create a new JIRA but when I clone an existing JIRA (that was created before introducing the Custom field), the newly cloned JIRA does not show the custom field.
Think I got it. I am not editing the old JIRAs with the custom field and that's the reason it's not carried forward to the cloned ones? I see that the custom field appears when I edit the cloned JIRA, but this step tends to be missed by most users resulting in quite a big number of JIRAs with blank category.
Is there a workaround?
Yes. The reason the field has no data is because you have not put data in it.
There is no "workaround" because there is nothing to work around. You have not got data in the field. You copy the issue, with no data in the field. So you have no data in the field. There is nothing you can possibly do here. I'm not sure how else I can say "you can't copy something that is not there"
I have this exact same problem, except I am entering data into the custom fields.
I have two ways of doing this, one is a post function on create, and the other is to manually edit the ticket after creation.
When cloning a ticket created in both ways, the custom fields are not cloned.
They are single select drop downs. Any ideas?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs