NOTE: This bug report is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding bug report.

      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:

      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 
      

      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.

      To Replicate

      1. 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)
      2. Create Project > Agile Software Development - Scrum. Proceed through steps to create.
      3. Attempt to create an issue in new project, Error: Could not find workflow status for issue [ ]
      4. View Issues Panel in Overview:
        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 ...
      5. 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.

      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. Alternatively for server please refer to our Internal Server Error when accessing Rapid board KB article.

        1. app.png
          app.png
          279 kB
        2. console.png
          console.png
          773 kB
        3. error_500.log
          23 kB
        4. JIRA_Agile_Version.png
          JIRA_Agile_Version.png
          68 kB

            [JSWCLOUD-11487] Internal Server Error on Agile Boards

            Jay Gao added a comment - - edited

            Hi,
            I saw the compatibility matrix here .
            It seems JIRA Agile 6.7 is only compatible with JIRA 6.3 and later versions.
            Any idea for the users who are using prior JIRA 6.3?

            Thanks!
            Jay

            Jay Gao added a comment - - edited Hi, I saw the compatibility matrix here . It seems JIRA Agile 6.7 is only compatible with JIRA 6.3 and later versions. Any idea for the users who are using prior JIRA 6.3? Thanks! Jay

            bmccoy added a comment -

            Hi David,

            6.7.0 is the version of Agile that will be released (its the version after 6.6.80). We are hoping to get this out to cloud on the 27th of April. With the usual disclaimer that things can happen out of our control, so the date may change.

            Cheers,
            Brydie

            bmccoy added a comment - Hi David, 6.7.0 is the version of Agile that will be released (its the version after 6.6.80). We are hoping to get this out to cloud on the 27th of April. With the usual disclaimer that things can happen out of our control, so the date may change. Cheers, Brydie

            David Ward added a comment -

            When is this version going to released to cloud users?

            Also what software suite does the version 6.7.0 relate to? I can see the Cloud JIRA version is 6.4-OD-16-006 but the Agile version is 6.6.80-D20150309T12523 neither of which is greater than the fixed version or does the fix version relate to something else?

            David Ward added a comment - When is this version going to released to cloud users? Also what software suite does the version 6.7.0 relate to? I can see the Cloud JIRA version is 6.4-OD-16-006 but the Agile version is 6.6.80-D20150309T12523 neither of which is greater than the fixed version or does the fix version relate to something else?

            In our case, the workflow step's linked status was deleted accidentally before the workflow was saved, so the workflow contains a step which is linked to an ID - that doesn't exist. This is a bit different than the original bug, but roots back to the board controlled workflow.

            Laszlo Kremer added a comment - In our case, the workflow step's linked status was deleted accidentally before the workflow was saved, so the workflow contains a step which is linked to an ID - that doesn't exist. This is a bit different than the original bug, but roots back to the board controlled workflow.

            dpandurangan1 please note that this is the public issue tracker. If you're running into issues with JIRA Agile installation and require support, you'll want to open a ticket at https://support.atlassian.com/ so that we can investigate the specific problem.

            Dobroslawa Wierzbicka (Inactive) added a comment - dpandurangan1 please note that this is the public issue tracker. If you're running into issues with JIRA Agile installation and require support, you'll want to open a ticket at https://support.atlassian.com/ so that we can investigate the specific problem.

            Hi,

            I am not able to Install Agile. Please assist me with the error.
            Senthil Kumar

            dpandurangan@apptiumtech.com added a comment - Hi, I am not able to Install Agile. Please assist me with the error. Senthil Kumar

            Got the same problem. Hope they can fix this soon. (I created a support ticket at atlassian)

            Theo van der Sluijs added a comment - Got the same problem. Hope they can fix this soon. (I created a support ticket at atlassian)

            Michele Caramello added a comment - - edited

            Hi,
            we have the same problem. We just created a new Project + Kanban board and when trying to either access the board or configure it we get the 500 error code with almost exact same error stack trace.
            See attachments:

            • Application screenshot
            • Chrome Console screenshot
            • Chrome Console log

            We use JIRA onDemand so as suggested above, I am going ahead and contacting support.

            Michele Caramello added a comment - - edited Hi, we have the same problem. We just created a new Project + Kanban board and when trying to either access the board or configure it we get the 500 error code with almost exact same error stack trace. See attachments: Application screenshot Chrome Console screenshot Chrome Console log We use JIRA onDemand so as suggested above, I am going ahead and contacting support.

            I've reclassified this issue as 'Major' priority in accordance with our Bug prioritising guidelines.

            Michael Tokar added a comment - I've reclassified this issue as 'Major' priority in accordance with our Bug prioritising guidelines.

              Unassigned Unassigned
              jrobison1 JordanA
              Affected customers:
              5 This affects my team
              Watchers:
              32 Start watching this issue

                Created:
                Updated:
                Resolved: