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

400 Bad Request in response to /rest/dev-status/1.0/issue/summary?issueId=undefined when using issue detail view on Agile board

    XMLWordPrintable

Details

    • 7.02
    • 35
    • Severity 3 - Minor
    • 43
    • Hide
      Atlassian Update – 12 June 2023

      Dear Customers,

      Thank you for taking the time to file and comment on this issue. We realise it still occurs and might be confusing when checking browser logs. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog.

      Little explanation and severity of this bug:
      We would like to explain that current log in console is not a symptom of wrong working instance. This is internal bug in development panel plugin which appears also in correct working instances.

      Please continue watching this ticket for future updates and changes.

      Best regards

      Adrian Wojtasik

      Jira Developer

      Show
      Atlassian Update – 12 June 2023 Dear Customers, Thank you for taking the time to file and comment on this issue. We realise it still occurs and might be confusing when checking browser logs. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog. Little explanation and severity of this bug: We would like to explain that current log in console is not a symptom of wrong working instance. This is internal bug in development panel plugin which appears also in correct working instances. Please continue watching this ticket for future updates and changes. Best regards Adrian Wojtasik Jira Developer

    Description

      Summary

      When opening issues in issue detail view on either Kanban or Scrum boards, request is sent to /rest/dev-status/1.0/issue/summary?issueId=undefined which receives a 400 Bad Request response because of the invalid issueId issueId=undefined.

      Environment

      JIRA Software 7.2 environment without any dev-tools integration*

      Steps to Reproduce

      1. On a freshly installed JIRA Software 7.2 instance, create an Agile Board (Kanban or Scrum doesn't matter)
      2. Populate the Agile project with a few issues
      3. Enable the development tools network tab of your browser
      4. From the Agile board, select any issue so that it loads in the issue detail view panel to the right.
      5. Observe than when you select an issue there is a request to /rest/dev-status/1.0/issue/summary?issueId=

      Expected Results

      These rest calls actual have the correct issue ID appended and return a 200 response e.g. /rest/dev-status/1.0/issue/summary?issueId=10000

      Actual Results

      The rest calls are missing a valid issue id and appear like /rest/dev-status/1.0/issue/summary?issueId=undefined. Note issueId=undefined

      Notes

      Interestingly the problem corrects itself, if you have these instance integrated with Develpment tools (e.g. Bitbucket, Github etc.) to activate the dev panel. Once you delete the Development tools integration the problem re-surfaces.

      Attachments

        Issue Links

          Activity

            People

              1c017edd2c81 awojtasik
              takindele Taiwo Akindele (Inactive)
              Votes:
              68 Vote for this issue
              Watchers:
              67 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: