-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
8
-
Problem Definition
After a custom field context change from global to per project, the custom field will disappear from screens in projects where it is not applicable.
However, The values of the custom field on issues from projects where it's not applicable are not removed from the database table customfieldvalue.
Suggested Solution
After a custom field context change to only apply to certain projects, all values of the custom field in issues that belong to the excluded projects should be deleted.
Workaround
- While a SQL DELETE statement is feasible, this option is to be avoided.
- A re-index will remove issues from searches in projects where it's not applicable.
- The UI will not display any values for this custom field in the excluded projects.
- duplicates
-
JRASERVER-17880 Deleting Custom Field Contexts does not remove options from database
-
- Gathering Impact
-