Jira Service Management shows 500 error on "Requests" page

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

問題

When customer navigates to Requests page in customer portal and tries to filter tickets by status a HTTP 500 error is thrown :


(info) Note that there is a separate KB article which also addresses the "500 error" thrown in customer portal. If the diagnosis steps from this KB article do not apply to your situation, please take a look at the other KB article 500 error when trying to create a request from the Service Management Customer Portal, which might be relevant.

環境

Any Jira Service Management (JSM) version from 4.0.0

診断

  • Check if you find the following exception in the Jira logs:

    2017-07-05 07:34:06,808 http-nio-8080-exec-79  url:/rest/servicedesk/1/customer/models username:toko  ERROR toko 454x6007348x1 7ddfj3 192.168.26.38,0:0:0:0:0:0:0:1 /rest/servicedesk/1/customer/models [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: None.get
    java.util.NoSuchElementException: None.get
    	at scala.None$.get(Option.scala:347)
    	at scala.None$.get(Option.scala:345)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$15$$anonfun$apply$1.apply$mcZ$sp(RequestListProviderScala.scala:260)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$15$$anonfun$apply$1.apply(RequestListProviderScala.scala:260)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$15$$anonfun$apply$1.apply(RequestListProviderScala.scala:260)
    	at scala.collection.mutable.MapLike$class.getOrElseUpdate(MapLike.scala:194)
    	at scala.collection.mutable.AbstractMap.getOrElseUpdate(Map.scala:80)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$15.apply(RequestListProviderScala.scala:259)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$15.apply(RequestListProviderScala.scala:258)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$17$$anonfun$apply$14$$anonfun$18.apply(RequestListProviderScala.scala:269)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$17$$anonfun$apply$14$$anonfun$18.apply(RequestListProviderScala.scala:269)
    	at scala.collection.LinearSeqOptimized$class.find(LinearSeqOptimized.scala:113)
    	at scala.collection.immutable.List.find(List.scala:84)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$17$$anonfun$apply$14.apply(RequestListProviderScala.scala:269)
    	at com.atlassian.servicedesk.internal.feature.customer.request.RequestListProviderScala$$anonfun$17$$anonfun$apply$14.apply(RequestListProviderScala.scala:267)
    	at scala.Option.map(Option.scala:146)
    	...
    	at com.atlassian.servicedesk.internal.feature.customer.portal.providers.AllReqFilterResponseProvider.getResponse(AllReqFilterResponseProvider.scala:41)
    	at com.atlassian.servicedesk.internal.rest.CustomerResponseFactory$$anonfun$com$atlassian$servicedesk$internal$rest$CustomerResponseFactory$$getResponse$1.apply(CustomerResponseFactory.scala:157)
    	at com.atlassian.servicedesk.internal.rest.CustomerResponseFactory$$anonfun$com$atlassian$servicedesk$internal$rest$CustomerResponseFactory$$getResponse$1.apply(CustomerResponseFactory.scala:156)
    	at scalaz.$bslash$div.flatMap(Either.scala:134)
    	at com.atlassian.servicedesk.internal.rest.CustomerResponseFactory.com$atlassian$servicedesk$internal$rest$CustomerResponseFactory$$getResponse(CustomerResponseFactory.scala:156)
    	at com.atlassian.servicedesk.internal.rest.CustomerResponseFactory$$anonfun$1.apply(CustomerResponseFactory.scala:63)
    	at com.atlassian.servicedesk.internal.rest.CustomerResponseFactory$$anonfun$1.apply(CustomerResponseFactory.scala:63)
    	...
    	at com.atlassian.servicedesk.internal.rest.CustomerResponseFactory.createResponse(CustomerResponseFactory.scala:63)
    	at com.atlassian.servicedesk.internal.rest.CustomerRestResource.modelRequest(CustomerRestResource.scala:27)
    	...
  • Use the following query to verify if there is any Request Type that does not have any associated fields. If the above query returns a non-empty dataset then the problem is caused by the Request type returned by the query, and this KB article is relevant.
    (info) The following SQL code is tested on PostgreSQL which may need to be adjusted in order to execute on other DB systems.

    select * from "AO_54307E_VIEWPORTFORM" vpform left join "AO_54307E_VIEWPORTFIELD" vpfield on vpform."ID"=vpfield."FORM_ID" where vpfield."ID" is null;

原因

There is a Request Type in the Jira Service Management project that does not have any associated field

ソリューション

Remove these request types (via the page Project Settings > Request Types) or add at least one field to the request type.

For more details on configuring Service Management request type please refer to this documentation.


最終更新日 2023 年 9 月 5 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.