• Type: Bug
• Resolution: Fixed
• Priority: Medium (View bug fix roadmap)
• Fix Version/s: 6.7.0
• Affects Version/s: 6.6.80
• Component/s: None
• Labels:

  • affects-cloud
  • affects-server
  • fixme
  • ondemand-support-workaround
  • saigon
  • st10
  • support

1. error_500.log

   17/Dec/2014 12:13 AM

   23 kB

   Michele Caramello

2. console.png

   17/Dec/2014 12:13 AM

   773 kB

   Michele Caramello

3. app.png

   17/Dec/2014 12:13 AM

   279 kB

   Michele Caramello

4. JIRA_Agile_Version.png

   31/Jul/2015 7:15 AM

   68 kB

   Jay Gao

[JSWSERVER-11487] Internal Server Error on Agile Boards

Bugfix Automation Bot made changes - 27/Mar/2019 11:26 PM

Minimum Version

New: 6.06

Owen made changes - 16/Oct/2018 1:04 AM

Workflow	Original: JAC Bug Workflow v2 [ 2851500 ]	New: JAC Bug Workflow v3 [ 2932865 ]
Status	Original: Resolved [ 5 ]	New: Closed [ 6 ]

Owen made changes - 25/Sep/2018 12:47 AM

Workflow

Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544212 ]

New: JAC Bug Workflow v2 [ 2851500 ]

Ignat (Inactive) made changes - 01/Feb/2018 12:07 PM

Workflow

Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550765 ]

New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544212 ]

jonah (Inactive) made changes - 02/Apr/2017 12:00 PM

Description

Original: The configuration pages can't be accessed. The big error modal window pops up and you get an "Internal Server Error" Here is what I see when I use firebug: {code} Got an error response with text that we don't know how to parse: {"status-code":500,"stack-trace":"java.lang.NullPointerException\n\tat com.atlassian.greenhopper.web.rapid.view.ColumnEditRequest$StatusDetails.from(ColumnEditRequest.java:145)\n\tat com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.asStatusEntry(ColumnEditHelper.java:330)\n\tat com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnStatusesModel(ColumnEditHelper.java:313)\n\tat com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnEditModel(ColumnEditHelper.java:185)\n\tat com.atlassian.greenhopper.web.rapid.view.RapidViewEditHelper.getEditModel(RapidViewEditHelper.java:139)\n\tat com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource$7.call(RapidViewEditResource.java:191)\n\tat {code} h4. Cause: A status label was renamed. In my example, from *To Do* to *TO DO*. When you try to access the board, it sees that *To Do* does not exist, so it attempts to create it again, since it requires it. But unfortunately, since *TO DO* is essentially the same, it fails. This is a problem with case sensitivity. *Note:* I think this only happens if you edit a status that is already there by default to use a different case. h4. To Replicate # Go to {{secure/admin/ViewStatuses.jspa}} View Statuses, edit a default status to be in all caps for the name (e.g. To Do > TO DO) # *Create Project > Agile Software Development - Scrum*. Proceed through steps to create. # Attempt to create an issue in new project, *Error: Could not find workflow status for issue [ ]* # View *Issues Panel* in Overview: {noformat}An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getUrl' in class com.atlassian.jira.projects.legacy.projectpanel.fragment.impl.StatusSummaryFragment$StatusUrlUtil threw exception java.lang.NullPointerException at legacy/templates/projectpanels/fragments/issues/statussummary.vm[line 18, column 50] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284) at ...{noformat} # Go to *Agile Simplified Workflow Scheme for Project* and try to click *View as text* next to *Agile Simplified Workflow for Project*, and you will get another error, *The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation.* You will still be able to go directly to the workflow from the main Administration screen and view as text. h4. The Workaround This issue can be fixed with a manual database change. If you're running into it in a Cloud instance, please contact [Atlassian Support|https://support.atlassian.com/]. Alternatively for server please refer to our [Internal Server Error when accessing Rapid board|https://confluence.atlassian.com/display/AGILEKB/Internal+Server+Error+when+accessing+Rapid+board] KB article.

New: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-11487].   {panel} The configuration pages can't be accessed. The big error modal window pops up and you get an "Internal Server Error" Here is what I see when I use firebug: {code} Got an error response with text that we don't know how to parse: {"status-code":500,"stack-trace":"java.lang.NullPointerException\n\tat com.atlassian.greenhopper.web.rapid.view.ColumnEditRequest$StatusDetails.from(ColumnEditRequest.java:145)\n\tat com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.asStatusEntry(ColumnEditHelper.java:330)\n\tat com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnStatusesModel(ColumnEditHelper.java:313)\n\tat com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnEditModel(ColumnEditHelper.java:185)\n\tat com.atlassian.greenhopper.web.rapid.view.RapidViewEditHelper.getEditModel(RapidViewEditHelper.java:139)\n\tat com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource$7.call(RapidViewEditResource.java:191)\n\tat {code} h4. Cause: A status label was renamed. In my example, from *To Do* to *TO DO*. When you try to access the board, it sees that *To Do* does not exist, so it attempts to create it again, since it requires it. But unfortunately, since *TO DO* is essentially the same, it fails. This is a problem with case sensitivity. *Note:* I think this only happens if you edit a status that is already there by default to use a different case. h4. To Replicate # Go to {{secure/admin/ViewStatuses.jspa}} View Statuses, edit a default status to be in all caps for the name (e.g. To Do > TO DO) # *Create Project > Agile Software Development - Scrum*. Proceed through steps to create. # Attempt to create an issue in new project, *Error: Could not find workflow status for issue [ ]* # View *Issues Panel* in Overview: {noformat}An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getUrl' in class com.atlassian.jira.projects.legacy.projectpanel.fragment.impl.StatusSummaryFragment$StatusUrlUtil threw exception java.lang.NullPointerException at legacy/templates/projectpanels/fragments/issues/statussummary.vm[line 18, column 50] at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284) at ...{noformat} # Go to *Agile Simplified Workflow Scheme for Project* and try to click *View as text* next to *Agile Simplified Workflow for Project*, and you will get another error, *The JIRA server was contacted but has returned an error response. We are unsure of the result of this operation.* You will still be able to go directly to the workflow from the main Administration screen and view as text. h4. The Workaround This issue can be fixed with a manual database change. If you're running into it in a Cloud instance, please contact [Atlassian Support|https://support.atlassian.com/]. Alternatively for server please refer to our [Internal Server Error when accessing Rapid board|https://confluence.atlassian.com/display/AGILEKB/Internal+Server+Error+when+accessing+Rapid+board] KB article.

jonah (Inactive) made changes - 02/Apr/2017 11:59 AM

Link

New: This issue relates to JSWCLOUD-11487 [ JSWCLOUD-11487 ]

Confluence Escalation Bot (Inactive) made changes - 16/Mar/2017 4:31 AM

Labels

Original: affects-server fixme ondemand-support-workaround saigon st10 support

New: affects-cloud affects-server fixme ondemand-support-workaround saigon st10 support

Confluence Escalation Bot (Inactive) made changes - 20/Feb/2017 2:58 AM

Labels

Original: fixme ondemand-support-workaround saigon st10 support

New: affects-server fixme ondemand-support-workaround saigon st10 support

Ben Magro (Inactive) made changes - 16/Jan/2017 2:31 AM

Remote Link

Original: This issue links to "Page (Extranet)" [ 107000 ]

Owen made changes - 07/Jul/2016 7:05 AM

Workflow

Original: JIRA Bug Workflow w Kanban v6 [ 906506 ]

New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550765 ]

Load more older events