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

      Currently, Team Managed projects' custom fields are not searchable easily without database access, and duplicate fields can cause issues with JQL (such as with the function "Sprint in openSprints()") if there are custom fields that share the same name. This prevents users from figuring out what custom field may be causing issues if Team Managed custom fields are interfering with JQL queries due to duplicate names, as there is no way to search for them and figure out if that is the case or not. It would also allow for easier management of custom fields in general to ensure that duplicates aren't created in the first place.

       

       

          Form Name

            [JRACLOUD-85929] Search needed for all custom fields across TMP and CMPs

            The watchers of this issue may also be interested in the following:

            • JSWCLOUD-18756 – Restrict Team-Managed custom fields name if already exists another custom field with the same name
            • JRACLOUD-68370 – Prevent users from creating custom fields using the same name as an existing system or custom field
            • 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 - The watchers of this issue may also be interested in the following: JSWCLOUD-18756 – Restrict Team-Managed custom fields name if already exists another custom field with the same name JRACLOUD-68370 – Prevent users from creating custom fields using the same name as an existing system or custom field JRACLOUD-74336 – Allow a way of identifying custom fields from company-managed and team-managed projects in the basic search

            Can we add an additional bug request that PREVENTS the creation of fields in team managed projects that have the same name as system fields?
            We just had some "interesting times" figuring out that many dashboards and filters stopped working as one team added the field "request type" as a custom field, breaking things left, right and center.

            Do we have a definite list of fields that must not be created in team-managed projects so far? I'd like to communicate those to our users before desaster strikes again

            Tobias Hüttenmüller added a comment - Can we add an additional bug request that PREVENTS the creation of fields in team managed projects that have the same name as system fields? We just had some "interesting times" figuring out that many dashboards and filters stopped working as one team added the field "request type" as a custom field, breaking things left, right and center. Do we have a definite list of fields that must not be created in team-managed projects so far? I'd like to communicate those to our users before desaster strikes again

              Unassigned Unassigned
              3176abc1c383 Hieuy Mac
              Votes:
              7 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: