JIRA Agile 6.6.70 changes the terms "Plan mode", "Work mode", and "Report mode" to "Backlog", "Active sprints"/"Kanban board", "Reports" respectively. For more information, see the JIRA Agile 6.6.70 release notes.

Skip to end of metadata
Go to start of metadata

Once you have chosen which issues are to be included in your next sprint, you are ready to start the sprint.

(info) This page only applies to Scrum boards.

Please note, you must have the JIRA 'Administer Projects' permission for all projects included in the board filter to start a sprint in that project. This applies even when respective sprint doesn't include issues from all projects.

To start a Sprint:

  1. Click the Agile link's down-arrow in the top navigation bar, then select your preferred board from the resulting dropdown menu.
  2. Click Backlog.
  3. Make sure the sprint footer (the grey horizontal marker) is positioned below the issues you want to include in your upcoming sprint. Drag it up or down, or drag issues up from the backlog, as needed.
  4. Click Start Sprint.

     Why is Start Sprint disabled?

    You will not be permitted to start a sprint, unless all of following conditions are met:

    • You can only start a sprint if there is no active sprint. While a sprint is active in Work mode, you can still plan subsequent sprints in Plan mode, but you won't be able to start one until the active sprint is completed. (You can, however, drag and drop an issue in Plan mode onto the active sprint.)
    • You will need to have the JIRA 'Administer Projects' permission in the project(s) included in the board. This means that if your board includes issues from multiple projects, you need to have the 'Administer Projects' permission in each of those projects.
    • Ranking must be enabled on the board.
    • Only the planned sprint at the top of the backlog can be started. If you want to start a sprint that is lower in the list, you'll need to Reorder the sprint to move it to the top of the backlog. (This doesn't apply when Parallel Sprints are enabled)

    (info) If you do not have an estimation statistic applied to an issue, you will receive a warning when starting the sprint (unless you are using Issue Count, as this is calculated automatically).

  5. You will be prompted to enter a sprint name and to select the Start Date and End Date for the sprint.

You will be taken to Active sprints, where your newly started sprint will now be shown.

17 Comments

  1. This cost me time. Disabled 'Start Sprint' link - if issue from several projects are used in a board projects have to be mentioned explicitly in the filter query. Otherwise you will need to give a user "Administer Projects" permission for all projects. Found here - https://answers.atlassian.com/questions/164780/greenhopper-create-sprint-permissions

  2. Someone has been able to start a sprint while another was already active for the same project. How? We've no idea. So now we have 2 active sprints with different start dates and the same end date. Is it a bug or a feature? Both active sprints are accessible from the Work view of the project but a Sprint filter allow to display 1 or the other.

    I would have joined a screenshot but I wasn't able to add it to this comment :/ Chrome issue?

    1. Hi Jean-David,

      This could happen if you have parallel sprints enabled, or you changed the filter on your board (after starting the sprint) so that it included issues that were part of an active sprint on another board.

      Otherwise, this sounds like a bug. You shouldn't be able to start a sprint, if you already have an active sprint. Can you raise a  support request and our support team can help you investigate further?

      Kind regards,
      Andrew

      1. Parallel sprints is not enabled (great feature by the way, I'll try the beta!! But it would be great to enable it per project and not over all projects) and filters haven't been changed.

        I opened a support request yesterday.

        1. Was your request solved? We've got the same bug.

          1. No it hasn't and it wasn't related to the Parallel Sprint new feature. Since it wasn't blocking for us and mostly a surprise, I agreed with them to let it go for me.

            1. I was able to reproduce my issue:

              When editing an issue in an active sprint, I'm able to change the sprint to another active one in another project. The result is 2 (or more) active sprints in the same project at the same time with different name.

  3. Is there any way to allow non-admins access to start sprints?  Maybe component leads?

    We have 14 teams.  I am leading an effort to get people off using either Trello or physical kanban boards.  A team will pick up an MVF that could touch several components.  Teams may work with different components on each MVF they pick up.  Only one team works an MVF.

    I have created one project for the main product, the component field for the applicable components (not used for much), and created an MVF ID custom field to differentiate MVFs.  A team lead copies a custom filter template, changes the MVF ID to their own, and saves a new filter.  The lead then creates a new scrum board based on that filter.  The lead owns the board and can make any customizations they like.

    However the lead cannot create or start a sprint unless they are an admin.  For this to work, I would need to make all 14 leads JIRA admins.  Not impossible, but not desirable.  Is there some way to grant them perms without making them admins, or is there some other workflow suggested?  I could switch the component to being the MVF ID if that would give the lead access to create sprint.

     

    1. There is a difference between JIRA Admin and Project Admin. Depending on your configuration JIRA Admin could also be Project Admin and create sprint.

      Project Admin have limited rights within a given project including sprint start/stop.

      Go into the Project Roles page in a given project Administration page and assign the desired users to the project roles call "Administrators". You can either add users one by one or put those users into a group and assign the group to the role.

      Hope it helps.

       

      1. face palm

        Thank you for picking up on my error.  Seems like that should work as fairly easy solution.  Huge relief!

         

  4. Got a project admin who can't start a sprint, he can add issues to one, but can't create or start. He has been given project admin right in permissions scheme, and admin role within the project. What am I doing wrong?

    1. I suspect that if your project admin cannot create or start a sprint that your board may include issues from other projects (that your project admin is not an administrator for). Trying checking the filter for your board.

      It could also be due to Ranking being disabled on the board or the board already having an active sprint, but these are usually more obvious.

      If none of these options help, please contact our support team and they can help you figure out what's going wrong.

  5. When you start a sprint, there's a two week sprint duration defaulted but it actually is two weeks 1 day forcing teams that use two week sprints to move the end date back a day. Is there a way or going to be a way to manage the default beginning and end sprint dates per project?

    Thanks.

    Pat

  6. In order to start and close sprints we need to give the user Project Administrator access, which also gives them too many undesirable permissions (such as editing versions, project role membership, project components).  This we find to be too much permission when all they really need to be able to do is control their own sprints.  Is there a plan to provide a role related just to managing sprints?

    1. Blair Dickey, there's an existing feature suggestion that seems to be covering your request. Feel free to review it and join the discussion in comments:  GHS-5035 - As a JIRA/GH administrator, I would like to be able to specify who is allowed to create and start a sprint independently from the "Administer Projects" JIRA permission Open

  7. Is there a way to change the default end date that is prepopulated at the beginning of the sprint? We operate on 1 week sprints and it's currently set to default at 2 weeks. 

    1. Marcy Stroup, please see this Suggestion: GHS-7809 - Ability to customize the default duration of a Sprint Closed