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

            Tair Tidhar made changes -
            Component/s Original: Issue - Navigation [ 46635 ]
            Tair Tidhar made changes -
            Component/s New: Issue - Search - Frontend only [ 77950 ]
            Anusha Rutnam made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Anusha Rutnam made changes -
            Link New: This issue duplicates JRACLOUD-74037 [ JRACLOUD-74037 ]

            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.
            Anusha Rutnam made changes -
            Link New: This issue is related to JSWCLOUD-23749 [ JSWCLOUD-23749 ]
            Anusha Rutnam made changes -
            Summary Original: Allow a way of identifying custom fields from classic and next-gen projects in the basic search New: Allow a way of identifying custom fields from company-managed and team-managed projects in the basic search
            Anusha Rutnam made changes -
            Link New: This issue is related to JSWCLOUD-18756 [ JSWCLOUD-18756 ]
            Anusha Rutnam made changes -
            Component/s New: Issue - Navigation [ 46635 ]
            SET Analytics Bot made changes -
            Support reference count Original: 4 New: 5

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

                Created:
                Updated:
                Resolved: