Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9726

Scripted function "inSprint" compilation failure

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Tracked Elsewhere
    • Icon: High High (View bug fix roadmap)
    • None
    • 6.3.0.1, 6.3.0.2
    • None

    • JIRA 5.2.11 (Download). Operating system: Windows 7.

      After updating from Greenhopper 6.2.5.1 to JIRA Agile 6.3.0.1 when trying to view a Sprint in the Issue Navigator we are receiving the following error message: 'Scripted function "inSprint" compilation failure. Contact administrator. Message: Function failed to execute http method - failed with code: 404' (see Capture.PNG).

      I have done a re-index and even tried to disable and renable the plugin with the same result. The update to the plugin was done through the Plugin Manager in JIRA. Our UPM is version 2.13.1.

        1. Capture.PNG
          Capture.PNG
          8 kB

            [JSWSERVER-9726] Scripted function "inSprint" compilation failure

            Gernot Eger added a comment -

            ... and https://jamieechlin.atlassian.net/browse/GRV-316 is fixed, so updating ScriptRunner fixes this as well

            Gernot Eger added a comment - ... and https://jamieechlin.atlassian.net/browse/GRV-316 is fixed, so updating ScriptRunner fixes this as well

            Chad Larkin added a comment -

            Take a look here, https://jamieechlin.atlassian.net/browse/GRV-316, for the issue in Script Runner

            Chad Larkin added a comment - Take a look here, https://jamieechlin.atlassian.net/browse/GRV-316 , for the issue in Script Runner

            Matthew Zach added a comment -

            Following up on this as it is still an issue. Fabian Meier, how can we contact Jamie Echlin?

            Matthew Zach added a comment - Following up on this as it is still an issue. Fabian Meier, how can we contact Jamie Echlin?

            Brandon Barlow added a comment -

            I replicated Matthew Zach's problem exactly - "View in Issue Navigator" link in Plan mode, JIRA Agile 6.3.0.2.

            Scripted function "inSprint" compilation failure. Contact administrator. Message: Function failed to execute http method - failed with code: 404

            Brandon Barlow added a comment - I replicated Matthew Zach's problem exactly - "View in Issue Navigator" link in Plan mode, JIRA Agile 6.3.0.2. Scripted function "inSprint" compilation failure. Contact administrator. Message: Function failed to execute http method - failed with code: 404

            Matthew Zach added a comment - - edited

            We got the same message (after upgrading to Jira Agile 6.3.0.2). Specifically we get this when we click the "View in Issue Navigator" link from the plan mode for a given sprint within Jira Agile.

            Matthew Zach added a comment - - edited We got the same message (after upgrading to Jira Agile 6.3.0.2). Specifically we get this when we click the "View in Issue Navigator" link from the plan mode for a given sprint within Jira Agile.

            Gernot Eger added a comment -

            I also observed this behaviour in Jira 6.0.5 when upgrading from GreenHopper 6.2.5

            Gernot Eger added a comment - I also observed this behaviour in Jira 6.0.5 when upgrading from GreenHopper 6.2.5

            Fabian Meier added a comment -

            mia.beckett, this is a Scriptrunner JQL function. The Greenhopper team will not be able to help you with that. Please contact Jamie Echlin instead!

            Fabian Meier added a comment - mia.beckett , this is a Scriptrunner JQL function. The Greenhopper team will not be able to help you with that. Please contact Jamie Echlin instead!

            Mia added a comment -

            Did update to 6.3.0.2 this morning and I am still receiving the error. The update had no warnings or failed messages, it was successful.

            Mia added a comment - Did update to 6.3.0.2 this morning and I am still receiving the error. The update had no warnings or failed messages, it was successful.

              Unassigned Unassigned
              7cfbdb9c54e1 Mia
              Affected customers:
              3 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: