Error reading issue data while loading Jira board

お困りですか?

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

コミュニティに質問

プラットフォームについて: Cloud、Server、および Data Center - この記事はすべてのプラットフォームに適用されます。

要約

While loading Jira board you would see an error 'Error reading issue data'.


診断

Log file

/rest/greenhopper/1.0/xboard/work/4498/colors.json [greenhopper.service.issue.IssueDataServiceImpl] A the following query was too complex to generate a query from: \{Sprint in closedSprints()} com.atlassian.jira.issue.search.ClauseTooComplexSearchException: A the following query was too complex to generate a query from: \{Sprint in closedSprints()} at com.atlassian.jira.jql.query.DefaultLuceneQueryBuilder.createLuceneQuery(DefaultLuceneQueryBuilder.java:31) at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:298) at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:157) at sun.reflect.GeneratedMethodAccessor1440.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26) at com.sun.proxy.$Proxy335.search(Unknown Source) at sun.reflect.GeneratedMethodAccessor1440.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) 

HAR file

/rest/greenhopper/1.0/xboard/work/4498/colors.json [web.rapid.work.WorkResource] JiraCopiedRestErrorCollection[errorMessages=[Error reading issue data],errors={}]


原因

The Card color is based on JQL which is returning more than 65000 results breaking the JQL function closedSprints(). 

This root cause is tracked on

JSWSERVER-20283 - Getting issue details... STATUS


ソリューション

If you plan to use the card color based on this same JQL  then you must do the following

  • Delete closed sprints
    You may consider deleting your older closed sprints to keep the number of closed sprints under 65,000. You may determine the oldest closed Sprints that are not needed anymore for reporting purposes, and remove them using the "Delete Sprint" operation (deleting closed sprints is possible after Jira version 7.9, ref. JSWSERVER-9220)
  • Increase the default limit of 65,000 
    This can be done by increasing the value for jira.search.maxclauses in jira-config.properties.
     Setting the parameter too high may have a performance impact on the system, hence please take care to increase the limit gradually (for example, if we're at 65,000 closed sprints already and currently closing 10,000K sprints/year, setting the limit to 85,000 will give us enough room for a couple of years already.)

The ideal workaround would be to modify the query in a way that it returns acceptable number of results.

最終更新日 2021 年 9 月 28 日

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

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