bug or feature (??)

[Consulente Atlassian]

I don't know if it's a feature I haven't really understood the use of, or it's yet another bug in Atlassian cloud applications. It's the list of fields you can insert in a Jira cloud dashboard view to enrich the information of the issues assigned to you. Why do fields like components or similar appear more than once? It would seem, but I repeat I didn't understand correctly... it's a bug, because who would like to see 10 times the "components" if he has 10 Jira cloud projects that use "components" in the issues?
Please help me understand

[Angélica Luz]

Hello Calogero,

Thank you for reaching out to Atlassian Community!

Testing on my local site I was able to identify that these fields that contains the same name is related to next-gen projects.

Next-gen is independent of classic and other next-gen projects, so it's possible to create on each project a field with the same name. 

In this case, one of the field Approvers, for example, was created by the system for classic projects (Jira settings > Issues > Custom fields) and the other one created on a next-gen project.

Here is an example where I created the field on different next-gen Service Desk projects:

Hope this clarifies!

Regards,
Angélica

[Deleted user]

@Angélica Luz in the meantime, I thank you for your answer. My perplexity is: how can I understand which of the many "Approvers" fields I show is the right one of the issue I want to use? Couldn't Jira  make it appear that I know on the right of the field the name of the Jira project to which the field belongs ?
It would be very easy.

[Angélica Luz]

Thank you for your suggestion. Based on that I created a feature request:

• Show the project key and custom field type for the duplicated custom fields when adding fields to a gadget

Please, click on vote and watch to receive updates about the feature.

For now, I believe that there is no known workaround. You can edit the name of the field to something different or manually add the project key.