Issues with Custom Fields showing in the Issue view of request types

Question

Hi everyone,

Although this is not a critical bug, it annoys my team after some time as we would like to add consistency to our working methods.

Problem statement
Fields keep populating the "Request Types/Issue View/Basic Fields" section of our project for all request types, degrading the agents' view of tickets.

An administrator did not add these fields to the request type settings, and removing them is a game of whack-a-mole. The fields do seem consistent, and they do not seem random. For example, the custom fields in our tenant, "project key" or "Change managers," would appear in all our request types and agent views.

We have 50+ request types on our project, and it is annoying to hide these fields from the agent's view constantly.

Any tips would be gladly appreciated.

Harry Coleman · Answer

Thank you Petru, I will sync with my team on this and get back to you.

Harry Coleman · Answer

Thank you for your warm welcome, John!

I appreciate your help with this. I will sync with my team on this, and we will try to find a solution to this.

Petru Simion [Simitech Ltd.] · Answer

Hi @Harry Coleman

To understand how fields are displayed in issues across projects, you need to grasp the following relationships:

1. Fields are placed on Screens.
2. Screens are added to Screen Schemes.
3. Issue Type Screen Schemes map each Issue Type to a Screen Scheme.
4. Issue Type Screen Schemes are used in one or more Projects.

Additionally, two critical configurations must be in place:

1. Field Configuration: The field must be visible (not hidden) for a specific project.
2. Field Context: The field must be allowed for specific projects and issue types.

Manually mapping these relationships for a single field can be time-consuming. For multiple fields, it becomes an enormous task.

To simplify this process, consider using Fields Dashboard for Jira , an app developed by our company. This app provides a clear, visual representation of how fields are used in projects, including:

- How fields are used in issue screens (create, edit, view)
- How fields are used in transition screens within workflows
- Field usage across projects and issue types

With Fields Dashboard for Jira, you can:

- View relationships at a glance
- Export data in CSV format for future reference
- Save significant time and effort

By using Fields Dashboard for Jira, you'll gain valuable insights into your field configurations and streamline your workflow.

Regards,

Petru