Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-74037

Issue search should distinguish between custom fields that have the same name

    • 31
    • 46
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      When you look for a custom field or status in JQL, Jira shows duplicated the fields but there is no clue to identify which project belongs to. 

      Steps to Reproduce

      1. Add a custom field with the same name in Next-Gen Project and classic
      2. Go to the Advanced search page and try to filter by this custom field
      3. The custom field appears two times, which is good but there is not a description to identify which is the project it belongs to.
      4. Same thing for statuses.  

      Expected Results

      Display the project it belongs to. 

      Or

      Display the custom field/status description.

      Actual Results

      Nothing is displayed:

      Workaround

      Quote the name and specify the project in the JQL sentence. 

            [JRACLOUD-74037] Issue search should distinguish between custom fields that have the same name

            I would see this in opposite way: do not show duplicated names at all, just show only one name without any pre/post suffix/differentiator. You want to search a FancyField in Project1? So 'project = Project1 and FancyField = value'. You want to search everywhere? so just 'FancyField = value'. Make it simpler and more universal and do not differentiate such fields. Differentiate them makes a filters/automations maintenance a nightmare.

            Bogdan Slusarczyk added a comment - I would see this in opposite way: do not show duplicated names at all, just show only one name without any pre/post suffix/differentiator. You want to search a FancyField in Project1? So 'project = Project1 and FancyField = value'. You want to search everywhere? so just 'FancyField = value'. Make it simpler and more universal and do not differentiate such fields. Differentiate them makes a filters/automations maintenance a nightmare.

            Sagi Gueta added a comment -

            Would be great to indicate or diffrintiate between COMPANY MANAGED PROJECTS to TEAM MANAGED PROJECT statuses. It's very frustrating to choose a status on my instance right now.

            Sagi Gueta added a comment - Would be great to indicate or diffrintiate between COMPANY MANAGED PROJECTS to TEAM MANAGED PROJECT statuses. It's very frustrating to choose a status on my instance right now.

            Dear,

            Strong request to solve this problem as it pollutes the look & feel for the End users, and does not encourage the acceptance of the Jira solution for our Business users

            Thank you

            Best regards,

            Rutger

            Rutger Koppelaar added a comment - Dear, Strong request to solve this problem as it pollutes the look & feel for the End users, and does not encourage the acceptance of the Jira solution for our Business users Thank you Best regards, Rutger

            The worse scenario is that Statuses are duplicated. Imagine 50 NG projects all w/ To Do, In Progress, Done. How would this even be manageable? Hopefully I have this wrong. Fortunately I don't use NG much at all.

            Jack Brickey added a comment - The worse scenario is that Statuses are duplicated. Imagine 50 NG projects all w/ To Do, In Progress, Done. How would this even be manageable? Hopefully I have this wrong. Fortunately I don't use NG much at all.

              gcardoso@atlassian.com Gonçalo Cardoso
              jgonzalez2@atlassian.com Jose Luis Gonzalez
              Votes:
              33 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated: