Hiding unused custom fields in workflow scheme changes

[Brendan Andrews]

We're using Jira server 7.4

There are literally hundreds of fields so when changing between workflow schemes I'm presented with tens of pages of fields asking me for destination statuses. (Unfortunately the custom fields were added to the Default scheme..)

I had thought that changing the project to use an issue type scheme (with only a handful of issue types) would just show the issue types in the scheme used in this project.

But it doesn't - it shows transitions for issue types the project doesn't use and doesn't even allow.

[Vasiliy Zverev]

We usually create field configuration sheme for similar projects where only used fields are specified.

More one advantage - when we use JQL like some field is not null - we get only issues where this field is assotiated with.

[Brendan Andrews]

Thanks - yes I've changed to an issue type scheme with just 5 issue types. But that hasn't helped.

The problem arises when you migrate a project to a new workflow. It doesn't show just the issues used, or even available in the applicable issue type scheme. It shows all of them which makes it a little tedious across many projects.