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

Allow a way of identifying custom fields from company-managed and team-managed projects in the basic search

XMLWordPrintable

    • 5

    • 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.

      Problem definition

      Currently, when using the basic search, it's not possible to distinguish between custom fields that were created for next-gen projects and the ones for classic projects.

      Impact

      When trying to use the basic search, if the custom fields have the same name, it's not possible to identify which ones are from the next-gen project (and which project), and the ones from the classic projects. This adds a level of difficulty on performing searches for specific projects or even to evaluate what custom fields are in use.

      Suggested resolution

      Add the possibility to distinguish classic and next-gen custom fields. Example: using a tag on the name.

            [JRACLOUD-74336] Allow a way of identifying custom fields from company-managed and team-managed projects in the basic search

            Anusha Rutnam added a comment -
            Atlassian Update - January 2024

            After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-74037 – Duplicated Field names in JQL Search which has more votes.

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - January 2024 After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-74037 – Duplicated Field names in JQL Search which has more votes. We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Denis Uschapivsky added a comment -

            Do you also want clients to be able to search for their queries, but because it doesn't recognize custom fields in the search, the search is not possible?

            My clients leave requests, but due to the fact that a large number of fields are custom, they cannot find their request. 

            Denis Uschapivsky added a comment - Do you also want clients to be able to search for their queries, but because it doesn't recognize custom fields in the search, the search is not possible? My clients leave requests, but due to the fact that a large number of fields are custom, they cannot find their request. 

              Unassigned Unassigned
              fbeck Fábio W. [Atlassian]
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: