-
Bug
-
Resolution: Fixed
-
Low
-
5.12.16
-
1
-
Severity 3 - Minor
-
5
-
Issue Summary
If a custom field is added to a request type in Jira Service Management (JSM) and later the related project is removed from the custom field context, it will prevent users from creating new issues with that request type in the customer portal and may also prevent users from seeing requests in the customer portal.
Steps to Reproduce
- Create a custom field of any type, then add a JSM project to its context
- Access the same JSM project, then go to Project settings (⚙ icon) > Request types
- Click on "Edit" for any request type, then add the custom field created in the previous step
- Go to Administration (⚙ icon) > Issues > Custom fields, then click on ... > Configure contexts for the custom field
- Remove the JSM project from its context, then save the changes
- Access the JSM project's customer portal, then try to create an issue with the related request type
Expected Results
The request is created successfully.
Actual Results
The request fails to be created. In the atlassian-jira.log file, the following error can be seen:
2025-05-23 16:07:39,645-0300 http-nio-8080-exec-24 url: /servicedesk/customer/portal/3/create/15, /rest/servicedesk/1/customer/pages/portal/3/create/15; user: rrosa ERROR rrosa 967x2478x1 y5x4l1 0:0:0:0:0:0:0:1 /servicedesk/customer/portal/3/create/15 [o.a.c.c.C.[.[localhost].[/].[default]] Servlet.service() for servlet [default] threw exception java.lang.NullPointerException: Cannot invoke "com.atlassian.jira.issue.fields.config.FieldConfig.getId()" because "fieldConfig" is null at com.atlassian.jira.issue.customfields.impl.LabelsCFType.getDefaultValue(LabelsCFType.java:154) at com.atlassian.servicedesk.internal.fields.defaultvalues.list.LabelCFDefaultValueProvider.getLabelsDefaultValues(LabelCFDefaultValueProvider.java:31) at com.atlassian.servicedesk.internal.fields.defaultvalues.list.LabelCFDefaultValueProvider.lambda$getDefaultValueIfValid$1(LabelCFDefaultValueProvider.java:24)
Workaround
- Remove the custom field from the affected request type OR
- Add the project back to the custom field context
- links to