Find out which custom fields are available for one issue type but not for another certain type

Question

We use Jira DC 8.20.3.

Is there a possibility to find out which custom fields are available for a certain issue type (e.g. A) but not for another certain issue type (e.g. B) ?

If I had an appropiate SQL for it, it would be fine, but if there is a better way to do it, I would prefer that way, of course.

Many thanks!

Nic Brough -Adaptavist- · Answer

I did say this in the answer, but I neglected to repeat it in explanations - the field context is about project and issue type.  The same "if it's global, you won't lose it" applies to change of type as well as project.

Gisela Lassahn · Answer

I do not want to move issues from one project to another but from one type to another (within the same project).

Therefore I have to know which custom fields are available for the first type but not for the other. I'm afraid that, if a custom field is not configured for the second type, the content of the field will be deleted during the move.

Nic Brough -Adaptavist- · Answer

Ok, that's actually great, in some ways.  It means you don't have any cases where you might have data loss!

If you move an issue from one project to another, Jira only deletes custom field data when the field does not exist for the new project.  Field configurations and screens are irrelevant to that, it's only the field context that matters.  As all your fields are "global", the fields exist in both source and target systems, so it won't be removed if you move the issues.

You may want to think about the field configs and screens if you want to see or use the field in the target project, but you are not going to lose data.