Issue Summary

      Jira 8.8 introduced a new behaviour where users can exclude Sprint created outside the board. In Jira 8.8 and above, if a board does not have any Sprint created on it and the board only display Sprint created outside the board through the board filter, the user will be seeing the following message while viewing Velocity Chart report:

      There are no available sprints for this board.

      Steps to Reproduce

      1. Create a new board with a board filter like: project = SSP ORDER BY Rank ASC
      2. On the board, create few Sprints.
      3. Add some issues to the Sprint.
      4. Start a Sprint and complete it.
      5. Repeat the step with the rest of the Sprints.
      6. Check the Velocity Chart on the board to verify that the Sprints are shown correctly.
      7. Create a new board with a similar board filter as the original board: project = SSP ORDER BY Rank ASC
      8. Navigate to the Velocity Chart on the board and we will see that report shows There are no available sprints for this board. message

      Expected Results

      • Velocity Chart shows the last completed Sprints.

      Actual Results

      Velocity Chart shows the following message and no Sprint is shown:

      There are no available sprints for this board.*

      Workaround 1

      Creating a new Sprint on the board affected board and completing it will allow the Velocity Chart to work again.

      • Create a new Sprint on the affected board.
      • Add an issue to the new Sprint.
      • Complete the Sprint.
      • Check the Velocity Chart on the affected board again.

      Workaround 2

      Making a REST API call to PUT agile/1.0/board/boardId/settings/refined-velocity through Postman, Curl or using the Atlassian REST API browser add-on.

      Using the Atlassian REST API Browser

      1. Let's install the Atlassian REST API Browser (this is a free tool that will add a REST API interface to help us apply the workaround easily)
      2. Navigate to Administration > System > REST API Browser
      3. Make sure the box "Show only public APIs" is not selected
      4. Enter your admin credentials to display all the REST API endpoints
      5. Search for the endpoint called
        agile/1.0/board/{boardId}/settings/refined-velocity
      6. Go to the PUT tab
      7. Insert the boardId of the board affected (this can be found at the Jira URL when you navigate to the board - it will be the something like "rapidView=2")
      8. Click on + Parameter
      9. Under the "Parameter" column, insert value
      10. Under the "Value" column, insert false
      11. At the "Request Body", make sure that we are sending an empty body like this:
        {
        
        }
      1. Click on Send
      2. Check if the Velocity Chart is working again
      3. Repeat the process to all boards affected

      Using the cURL command in a terminal window

      curl -X PUT -u $USERNAME -H "Content-Type: application/json" "JIRA_URL/rest/agile/1.0/board/boardId/settings/refined-velocity?value=false" -d "{ }"

      Don't forget to replace the $USERNAME, JIRA_URL and boardId above

            [JSWSERVER-20571] Velocity Chart is broken if no Sprint created on Board

            Same here, Just upgraded to 8.13 and experiencing this

            Eldad Dayagi added a comment - Same here, Just upgraded to 8.13 and experiencing this

            Jim Butler added a comment -

            did it come back in 8.13?  we are seeing this issue and the workaround does not seem to work.

             

            Jim Butler added a comment - did it come back in 8.13?  we are seeing this issue and the workaround does not seem to work.  

            Bug no longer occurs on Jira 8.9.0 and later. I'm closing this ticket as solved.

             

            Cheers,
            Paweł
            Jira Bugfix Team

            Pawel Przytarski added a comment - Bug no longer occurs on Jira 8.9.0 and later. I'm closing this ticket as solved.   Cheers, PaweÅ‚ Jira Bugfix Team

            Work around 1 doesn't persist and the issue comes back. Will try using the API call and see if that solution persists. 

            Omar Rashid added a comment - Work around 1 doesn't persist and the issue comes back. Will try using the API call and see if that solution persists. 

            This issue is critical for most of the companies I work with as it doesn't allow teams to share sprints or view overall progress on a different board.

            It's important to note that the button of "Hide unrelated sprints" doesn't work when the new board doesn't "own" any sprints.

             

            Since the offered workaround makes irrelevant data on the velocity chart, we did something else:

            I was able to overcome the issue by running a script of the REST API command: PUT to rest/agile/1.0/board/{boardId}/settings/refined-velocity?value=false

            When any user in the system changes the "Hide unrelated sprints" state, the problem comes back (value=true) again until the next script run.

            Elad Ben-Noam added a comment - This issue is critical for most of the companies I work with as it doesn't allow teams to share sprints or view overall progress on a different board. It's important to note that the button of "Hide unrelated sprints" doesn't work when the new board doesn't "own" any sprints.   Since the offered workaround makes irrelevant data on the velocity chart, we did something else: I was able to overcome the issue by running a script of the REST API command: PUT to rest/agile/1.0/board/{boardId}/settings/refined-velocity?value=false When any user in the system changes the "Hide unrelated sprints" state, the problem comes back (value=true) again until the next script run.

              Unassigned Unassigned
              vshanmugam Vicknesh Shanmugam (Inactive)
              Affected customers:
              10 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: