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

[Gisela Lassahn]

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-]

This is not a nice thing to try to get out of the database - for every project/issuetye combination you could have a different field context, issue type screen scheme, multiple screen schemes, multiple screens, field configuration scheme, and multiple field configurations., all held in different ways in the database and read in different ways.

However, you could simplify the "custom field available" to the technical definition - fields are available on any issue type that has the context.  It doesn't matter if you hide it with a Field Configuration by not putting it on a screen - it's still "available".

If you're ok with that definition, then you can see all of it in one place.  Go to Admin ->. Issues -> Custom fields, and look at the middle columns.  Fields with a global context are available to all projects.  It'll list the project/issue context for any limited fields.

[Gisela Lassahn]

We have got 109 Custom Fields, nearly all of them available for all projects.
And we have got 143 active projects.

For some of these projects (~10) I want to move the issues of a certain type to another certain type via a bulk change.

Beforehand, I want to know which data (custom field values) could get lost during the move. Therefore I'm searching for fields which are available for the first type but not for the second, independent of the project.

The relevant projects all use the Default Field Configuration and do not use a special Field Configuration Scheme.

I know the view you mentioned in your answer, but in the column "Available contexts" I can only see entries saying "Global (all projects)" or entries like "8 projects" but no entries to show me whether the fields are available for all types or not. But I'm sure we have custom fields which are only available for certain types.

Is there any place where I can see this without opening the configurations of all 109 custom fields and checking them manually?

[Nic Brough -Adaptavist-]

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.

[Gisela Lassahn]

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-]

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.