-
Suggestion
-
Resolution: Unresolved
-
66
-
59
-
You can create a custom field for company-managed projects and another for team-managed projects with the same name.
In advanced search when you start typing to fill the field name both appear but there is nothing to identify if one is for classic and the other for next-gen and this can cause confusion.
A suggestion is to don't allow to use the same name if it already exists.
- duplicates
-
JRACLOUD-68370 Prevent users from creating custom fields using the same name as an existing system or custom field
- Gathering Interest
- is related to
-
JRACLOUD-83050 Duplicate Custom Field Names in Team Managed Project is causing issues with JQL results
- Closed
-
JSWCLOUD-20905 Team-managed projects to share custom fields
- Closed
-
JRACLOUD-74037 Issue search should distinguish between custom fields that have the same name
- Gathering Interest
-
JRACLOUD-77919 Exporting issues creates duplicate columns when the same custom field name is used in both Company-managed and team-managed projects
- Gathering Interest
-
JSWCLOUD-23749 Search needed for all custom fields across TMP and CMPs
- Gathering Interest
- relates to
-
JRACLOUD-79845 Saved filter for the JQL breaks with when user create the same custom field name in Team Managed Project as of Company Managed Project.
- Closed
-
JSWCLOUD-20760 REST API endpoint (Get user default columns) returns incorrect columns with duplicate custom fields
- Closed
-
JRACLOUD-74336 Allow a way of identifying custom fields from company-managed and team-managed projects in the basic search
- Closed