There's no easy way to do that - you need to read the field contexts, all the field configurations for the project, then the three screens in each of the screen schemes, the screens in the workflow, and any functions in the workflow that might be using them.
Take a step back and ask "why"? What does the custom field usage per project tell you? Why do you think you need it?
A report needs to be made from my part. And there I need to mention number of custom fields per project.
And I think there is a groovy script for finding custom fields in complete JIRA, but I am unable to figure out how to run it for a particular project.
If you can help me with that, please respond.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Again, the question is "why", because you need to establish whether all the places a field *could* be used by a project need to be scanned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.