General sprints in Atlassian Jira Software


    In this article, I would like to talk about Shared Sprints in Atlassian Jira Software.

    If you read the official documentation, for example, here , then there will not be such a thing as a general sprint.

    For the first time I met the term general sprint here . This article is well explained what common sprints are and how to live with them.

    General sprints are an important concept in Atlassian Jira Software, because familiarity with general sprints occurs, as a rule, unexpectedly, and it seems that something went wrong. But this is not the case, and if you know how general sprints work, then you can use them for your needs.

    In this article, I will show with examples how the general sprints look and how to distinguish them from ordinary sprints. And also I will tell about their features.

    I tried all the examples in this article in the Jira Software Cloud and in the Jira Software Server 7.12.3.

    What is a common sprint?

    A common sprint is a sprint that is visible on more than one board.

    For example, there are such screenshots of the boards:

    SCRUM Board :

    SCRUM2 Board :

    You can see that on the SCRUM and SCRUM2 boards there is a sprint called SCRUM Sprint 3. This sprint is visible on two boards. Does that mean we see a total sprint? Not. In Jira Software there can be two different sprints with the same name.

    How to see the sprint going?

    In order to understand the general sprint in front of us or normal, we must look at the id of these two sprints.

    You can see the sprint id like this:

    If you hover the mouse over the button highlighted in the picture above in red, we will see the url, which will end in sprintId = <number>. This number is the sprint id. In our case, the two sprints went different, which means that we are not in a common sprint, but two regular sprints.

    General sprint

    Now let's take a look at this screenshot:

    In the screenshot we see the SCRUM board, on which there are two sprints with the same name. And the sprint highlighted in red contains the same ticket as the sprint on the SCRUM2 board. If we check the ID of this sprint on the SCRUM and SCRUM2 board, then the ID will match, which means that we have a common sprint.

    Why do we have the same sprint on two boards?

    Tickets that are visible on the board are selected by filters that are defined for the boards. You can see the filters if you go to the Board Settings -> General menu. This is how the filters for boards look like:

    SCRUM board :

    project = SCRUM OR priority is not EMPTY ORDER BY Rank ASC

    SCRUM2 board :

    project = SCRUM2 ORDER BY Rank ASC

    We see that the filter for SCRUM selects not only tickets from the SCRUM project, but also all tickets in our Jira instance that have priority filled, which means that it also selects tickets from the project SCRUM2. Therefore, tickets from the SCRUM2 project are visible both on the SCRUM board and on the SCRUM2 board. And so if we fill in the Sprint field in one of the tickets, this sprint will appear on two boards.

    A sprint is created from the board and contains a link to the board from which it was created. To do this, you can perform, for example, rest / agile / 1.0 / sprint / sprintId and see the board from which the sprint was created. In our case, we get the following result:

    {"id":5,"self":"","state":"active","name":"SCRUM Sprint 3","startDate":"2018-09-23T06:33:01.266Z","endDate":"2018-10-07T06:33:00.000Z","originBoardId":3,"goal":""}

    originBoardId = 3, and this is the SCRUM2 board. This means that the sprint was originally created on the SCRUM2 board, and it appeared on the SCRUM board because the sprint ticket is on both the SCRUM2 board and the SCRUM board.

    How do the general sprints behave?

    If you make any changes to the total sprint on any of the boards on which the sprint is visible, then the changes will be visible on all the boards.

    For example, if we rename a sprint on the SCRUM board, it will be renamed on the SCRUM2 board. If we close the sprint on the SCRUM board, it will close on the SCRUM board.

    This behavior is usually met by users. They work with a sprint and suddenly the sprint closes. None of the team did not close it. As a result, it turns out that the sprint was closed from another board, in which the filter selects tickets from this project.

    How can you use common sprints?

    Suppose we have several teams, and each team has its own project. Each team creates a board and works on this board. We want to see the sprints of all teams. How can we do this?

    • We can ask to share all the boards for us, and then we can see the sprint, if we go to the desired board.
    • We can create a board that will pick tickets from all the teams' projects. In this case, we will see information on all sprints on one board, which will require less effort from us to view all team sprints. But we must not forget that any actions with the sprint on our board will entail the same changes on the teams' boards.

    That is all I wanted to tell in this article. I hope you find the information useful.

    Also popular now: