nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom Field not appearing in a Cloned JIRA

Deepa Narayanan2

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.

Thoughts?

Thank you.

Accepted answers

Nic Brough -Adaptavist-

It won't - you haven't put any data in it. JIRA hides empty custom fields on the issue view to try to declutter the screen a bit. Try editing the issue to check the field is offered to you during edits.

Graeme Baker

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?

All comments

Nic Brough -Adaptavist-

Deepa Narayanan2

Sorry, I don't understand what you mean by 'you haven't put any data in it'. The custom field does have a drop down list of values.

Nic Brough -Adaptavist-

Work through what you have done:

Create an issue ABC-123
Add a new custom field to the system
Clone ABC-123 to ABC-457

At what point did you put data into the field ?

Deepa Narayanan2

Create an issue ABC-123
Add a new custom field to the system, with drop down values
Clone ABC-123 to ABC-457 - ABC 457 does not show up the Custom field

Graeme Baker

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?

Matt Wilson_grxhwo

Did you ever get a resolution on this? I'm seeing a similar issue right now, all my custom fields are being cloned except for my single select drop down.

I believe this behavior is new since upgrading from 7.4 to 7.10, but I could be wrong about that. I'm pretty sure I can band-aid this with script runner for now...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-core