Can you use migrated custom fields?
Asked by lapacquah.bryant:

Hello,

I have a custom field that was migrated, however is listed on request type A. I need to add it to Request Types (B and C). However Its stating **"Fields unavailable in the issue view".**

Can we reuse custom fields that have been migrated?

Thank you


Answers:
author: Walter Buggenhout
body: Hi [@lapacquah.bryant](/t5/user/viewprofilepage/user-id/4876239),

Yes, sure. It is very well possible that they are not on the screens associated with the issue type linked that is associated with this request type. If they are not on those screens, you can't use them on request type forms either.

Hope this helps!

comments: author: lapacquah.bryant
body: Thank you [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225) ,

The custom field is in the same project and screen. However I am receiving this message.

![Screenshot 2024-03-28 at 8.59.27?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/315141i324F6D37C4408C94/image-size/large?v=v2&px=999 "Screenshot 2024-03-28 at 8.59.27?AM.png")![Screenshot 2024-03-28 at 9.02.22?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/315140i57732185F3686534/image-size/large?v=v2&px=999 "Screenshot 2024-03-28 at 9.02.22?AM.png")

![Screenshot 2024-03-28 at 9.05.53?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/315142i9E060F4675AB10E9/image-size/large?v=v2&px=999 "Screenshot 2024-03-28 at 9.05.53?AM.png")

The same custom field **"End date"** is also on another Request Type in the same project/screen.

Thank you for the follow up.


author: Walter Buggenhout
body: Have you clicked that blue link in the error message? That usually points you in the right direction as to why you're not seeing the field.

But, judging from the message itself, it seems that the field *end date* is not configured to be used in either your project or the issue type associated with the request type. In Jira Settings \> Issues \> Issue Types, locate the custom field *end date* and check its settings, more specifically the fields *context*.

You may - on a side note - also find out that there are multiple custom fields with the same name in your site. So it's also worth checking if you're working with the right field in your project.


author: lapacquah.bryant
body: Thank you for update.

Yes I did review however it wasn't clear on what needed to be done next.

Based on the context and config details it looks like this custom field is **Global (All Issues)**. Which to me means I can use it anywhere. Please correct me if I am incorrect. Do I need to select a Issue Type?

![Screenshot 2024-03-28 at 11.16.31?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/315201i4574B88960ED6506/image-size/large?v=v2&px=999 "Screenshot 2024-03-28 at 11.16.31?AM.png")

Yes I have looked to make sure I am using the correct field, its only one End date listed in the Field section of project. The customer I am working with requested "**End date"** cf because they have it on another ticket. Its strange that its on one Request Type in the same project/screen and we cannot use it for other Request Types in the same setup.

Any other ideas?

Thank you


author: lapacquah.bryant
body: Good morning please review and provide feedback.

Thank you


Tags: cloud

jira-service-management

jira-service-management-cloud