-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
8
-
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.
- is related to
-
JRACLOUD-74037 Issue search should distinguish between custom fields that have the same name
- Gathering Interest
- relates to
-
JRACLOUD-74336 Allow a way of identifying custom fields from company-managed and team-managed projects in the basic search
- Closed
-
JRACLOUD-77547 Hide Team Managed fields from Advanced Search
- Closed
-
JRACLOUD-68370 Prevent users from creating custom fields using the same name as an existing system or custom field
- Gathering Interest
-
JSWCLOUD-18756 Restrict Team-Managed custom fields name if already exists another custom field with the same name
- Gathering Interest