JIRA Agile ドキュメント

Jira Agile 6.3
GreenHopper 6.2
GreenHopper 6.1

More...

Agile Knowledge Base Resources

子ページ
  • Internal Server Error when accessing Rapid board
メタデータの末尾にスキップ
メタデータの先頭に移動

症状

The following error shows up when accessing a Rapid board : 

 

atlassian-greenhopper.log に次のメッセージが表示される。

2015-01-26 10:23:46,461 http-bio-6312-exec-6 ERROR abcd 623x689x1 viw50s 0:0:0:0:0:0:0:1 /rest/greenhopper/1.0/rapidviewconfig/editmodel.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null
java.lang.NullPointerException
	at com.atlassian.greenhopper.web.rapid.view.ColumnEditRequest$StatusDetails.from(ColumnEditRequest.java:148)
	at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.asStatusEntry(ColumnEditHelper.java:331)
	at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnStatusesModel(ColumnEditHelper.java:314)
	at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnEditModel(ColumnEditHelper.java:186)
	at com.atlassian.greenhopper.web.rapid.view.RapidViewEditHelper.getEditModel(RapidViewEditHelper.java:147)
	at com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource$8.call(RapidViewEditResource.java:219)
	at com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource$8.call(RapidViewEditResource.java:212)
	at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:42)
	at com.atlassian.greenhopper.web.AbstractResource.createResponse(AbstractResource.java:100)
	at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:81)
	at com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource.getEditModel(RapidViewEditResource.java:211)  <+3> (NativeMethodAccessorImpl.java:57) (DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)  <+19> (DispatchProviderHelper.java:234) (DispatchProviderHelper.java:100) (DefaultMethodInvocation.java:61) (ExpandInterceptor.java:38) (DefaultMethodInvocation.java:61) (DispatchProviderHelper.java:132) (DispatchProviderHelper.java:230) (ResourceJavaMethodDispatcher.java:75) (HttpMethodRule.java:288) (RightHandPathRule.java:147) (ResourceClassRule.java:108) (RightHandPathRule.java:147) (RootResourceClassesRule.java:84) (WebApplicationImpl.java:1469) (WebApplicationImpl.java:1400) (WebApplicationImpl.java:1349) (WebApplicationImpl.java:1339) (WebComponent.java:416) (ServletContainer.java:537)

診断

Integrity checker does not return any errors or the issue persists after fixing all errors pointed by Integrity checker.

原因

There are some workflows contain steps that do not have a linked status.

回避策

Deleting the workflow and replacing it with another will effectively workaround the issue. This does mean the workflow is permanently gone. To attemp to address the problem please refer to the resolution below.

ソリューション

In order to find out the workflows that have this problem,

  1. Check the filter query for the Rapid Board. 
  2. List down all the projects that the Rapid board is pointing to. 
  3. Check the workflow for these projects. 
  4. One of the workflow step would be showing up like this :
  5. Restore the Linked Status by editing the workflow
    Click Edit button under that Step Operations to re-link the Linked Status
    (warning) This can only be done when the workflow is not active. To workaround this, create a copy of the active workflow and edit the Linked Status there.

If it's not possible to re-link the Linked Status:

  1. View the broken workflow, and generate an XML export of that workflow
  2. Open the XML file in a text editor, and search for any broken section like:

    <step id="6" name="In Progress">
    <meta name="jira.status.id">
    {STATUS_In Progress}</meta>
    </step>

    Then, replace it with the correct Step

    <step id="6" name="In Progress">
    <meta name="jira.status.id">3</meta>
    </step>

    (info) Replace the {STATUS_In Progress} with the correct ID of the missing Status. In this case, In Progress' ID is 3

  3. Save the changes, and upload the edited XML file as a new workflow from your Administration > Issues > Workflows page, by clicking the (+) Add Workflow button
  4. Since this is a workflow from an Agile project, go to the Workflow Scheme page, and click the Edit button for the affected project
  5. Click the Add Workflow > Add Existing button, and choose the fixed Workflow
  6. Click Next and associate it to All Unassigned Issue Types only
  7. Publish the changes, and associate any issue(s) when needed
  8. Verify whether the fixed workflow solve the issue

If any of the above steps did not help, please raise an issue with Atlassian Support with a Support zip and an XML backup of your instance.

 

Help us improve!

 

 

  • ラベルなし