The problem:
We have 1000's of fields in our JIRA instance with several custom fields added over a number of years. As a result, in a Company Managed Project, I have two problems:
- Too many fields in issue displays (which I have control to trim down)
- When I create widgets, dashboards, write JQL's, the search brings all the 1000's of fields. For e.g. we have more than a dozen variants of Priority fields. So all these variants are displayed in predictive options when I compose a JQL/filter.
- When I do bulk editing of issues, all 1000's of fields are displayed
- When I do bulk issues upload, all 1000's of fields are displayed for mapping.
All of the above makes it harder and slower to use the feature.
How I understand I can solve this:
I am aware I can set up field configurations to ensure I limit which among those 1000's of fields I wish to limit in my project and associate this new field configuration to Issue Types.
Question:
Whilst field configuration will solve what fields are exposed for the issue types in a project, when I write JQL/filter, or use fields in widgets, dashboards, given that I would have a field configuration, would the scope of fields that are shown to me be limited to what I configured in the field configuration (or) will the issue search screen (JQL), widgets, dashboards still continue to show me all the 1000's of fields despite of having a dedicated field configuration for my project.
What I would like is - if my query/filter has "Project = X", then I hope and would like only the fields that are configured for this project to be displayed. Is this how it would work ? Or wouldn't?
