Skip to end of metadata
Go to start of metadata

Once you have identified that an issue is due to be actioned, you will need to add it to a sprint. You can either add an issue to a future sprint, or to the sprint that is currently in progress (the active sprint).

There are three different methods for adding an issue to a sprint.

  • Add existing issues to a sprint — Use this when the issue already exists, and you want to add the issue to an active or future sprint.
  • Create and add a new issue to an active sprint — Use this when the issue does not exist, and you want to quickly add it to an active sprint.
  • Edit the Sprint field for an issue — Use this when editing an issue, and you know the name of the sprint.

(info) Please note:

  • This page only applies to Scrum boards.

  • Sub-tasks cannot be moved independently of their parents.
  • You will need to have the 'Edit Issue' permission in the project to which the issue belongs.
  • If you are moving the issue above or below other issues, you will need to have the 'Schedule Issue' permission in the project to which the issue belongs.

Adding an existing issue to a sprint

You can add existing issues to an active or future sprint, using the Backlog of a board. Please note:

  • adding an issue to an active sprint will be shown as a 'scope change' event on the Burndown Chart for that sprint.
  • adding an issue to a sprint on one board will affect all other boards which contain that issue.

To add an existing issue to 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. Select the issue(s) (use Shift+Click or Ctrl+Click) and right-click, then select the relevant sprint (see screenshot below).
    Alternatively, you can drag-and-drop individual issues onto the relevant sprint.

Screenshot: right-clicking an issue to send it to a sprint

 

Creating and adding a new issue to an active sprint

You can add existing issues to an active sprint, using the Active sprints of a board. Please note:

  • adding an issue to an active sprint will be shown as a 'scope change' event on the Burndown Chart for that sprint.
  • adding an issue to a sprint on one board will affect all other boards which contain that issue.
  • you must have the 'Administer Projects' permission for the projects included by the board's filter, otherwise the issue will be added directly to the backlog.

To create and add a new issue to an active 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 Active sprints.
  3. Click Create issue in the header to create the issue and complete the issue details, as desired.
  4. After creating the issue, a confirmation dialog will display. In the dialog, click Add to <sprint name> where <sprint name> is the name of the sprint that you are currently viewing on the board.

Screenshot: confirmation dialog with link to add new issue to current sprint

Editing the Sprint field for an issue

You can add issues to a sprint by doing the following:

  • Edit the Sprint field for a single issue: Add an issue to a sprint by creating/editing the issue and updating the Sprint field. The Sprint field is available when creating/editing the issue in both JIRA and JIRA Agile. Note:
    • You may need to show the field on the 'Create Issue'/'Edit Issue' dialog — choose Configure Fields then select the Sprint field.
    • You will only be able to choose from active or future sprints, i.e. closed/completed sprints will not be available for selection. 
    • You can edit the Sprint field in JIRA Agile 6.3.8.x and earlier, but you will need to configure your edit issue screen to show the Sprint field. Also, the Sprint field will not allow for searching by name — you will need to enter the Sprint ID.
  • Edit the Sprint field for multiple issues: Bulk edit issues and update the Sprint field, to add multiple issues to a sprint. Note, bulk edit currently does not allow you to search for Sprint by name, so you will need to enter the sprint ID. To find the Sprint ID, navigate to an issue in the sprint, hover over the sprint name and look in the URL for the number in the sprint parameter. 

Screenshot: Editing the Sprint field for an issue

29 Comments

  1. This functionality desperately needs keyboard shortcuts!

    Things I frustratingly have to reach for the mouse for on a daily basis:

    • Switching between Plan / Work / Report views
    • Adding/removing issues from a sprint
    • Filtering by epic
    • Creating a new issue in an epic
    • Moving between the sprint and backlog in plan view

    If these were at very least available from the Operations menu that would make a huge difference.

  2. Right at the point of creating a story or defect, I often want to assign it to an upcoming sprint. It would be a big timer saver if there was a way to do this from an issue. Currently I waste a lot of time having to navigate to the agile board and move it from there each time.

    1. At the time of creating the issue, set the Sprint field to the upcoming sprint.

  3. Agree, add a bug, move to the plan board, move the bug, confirm that it breaks the current sprint commitment and then move back into the work mode again takes alot of time. In our organization we think it has been working very well just to plan for some air in the iteraiton/sprint and then simply add found bugs into the iteration as they are being discovered. Using JIRA Agile 6.0 this will take alot more time (sad).

  4. Yes, I would love to use the Scrum board in a bit more flexible way too.

    This would be awesome: being in the work tab, hit c to create new issue, and assign it directly to the current sprint (or any other sprints for that matter). 

  5. Paul, you can hit 1, 2, or 3 to switch between Plan, Work, Reports respectively.

    1. Thanks Shawn. We're stuck on Greenhopper 6.1.6 here which unfortunately doesn't (seem to) have this feature. Something to look forward to when we upgrade I guess!

  6. Paul, Andy & Christoffer: I just found out that a solution on the I-want-to-add-an-issue-directly-into-a-sprint-problem actually has been addressed in the JIRA Agile version 6.3.4, you'll find the description here: JIRA Agile 6.3.4 Release Notes. Looks OK!

    1. Wohoo! Much (heart) for Atlassian, you're da best

  7. After creating the issue, a confirmation dialog will display. In the dialog, click Add to <sprint name> where <sprint name> is the name of the sprint that you are currently viewing on the board.

     

    We are all on JIRA Agile v6.3.5.3.  However, some users have this functionality but others do not.  Is there some other setting that controls which users have this option available?

    1. Hi James,

      Do your users (who do not have this functionality) have the 'Edit Issue' and 'Schedule Issue' permission in the project?

      Kind regards,
      Andrew

      1. Thank you for the reply and apologies for my late response.

        I can confirm that the users have the edit and schedule permission in the project.

        1. Hi James, 

          We have the following bug raised,  GHS-10262 - Creating and Adding new issue to active sprint does not work with documented project permissions Open , there is also two workarounds listed in the bug report.

  8. Hi Andrew,

    The problem James Yoon describes is also effecting me although I have the correct permissions ( edit and schedule). We are using JIRA Agile version 6.3.6.1.

    Regards,

    Marcel

    1. Hi Marcel and James,

      I'd recommend creating a support ticket, as there could be a number of reasons for this behaviour. Our support team will be able to help you figure out what's going wrong.

      Kind regards,
      Andrew

    2. Hi Marcel, 

      We have the following bug raised,  GHS-10262 - Creating and Adding new issue to active sprint does not work with documented project permissions Open , there is also two workarounds listed in the bug report.

      1. Adding the permission to 'Administer Projects' does allow the 'Add to <sprint name> dialog to be shown.

         Still, this does not work (meaning the "Add to <sprint name> dialog is not shown),  although all the my permissions are correct. As Andrew suggested, I will raise a support request.

        A functionality should just work, working around is not an option.

        THX.

  9. It would be great to be able to be able to add a sub-task to a sprint.  That way, you could break your larger task into multiple sub-tasks and do them in different sprints.  What is the rationale for preventing this?

    1. Rowan, I believe that in agile generally a task should be of a size that it can be done in a sprint. If it is bigger, you probably should split it into multiple tasks and link them using an epic. 

      I do wish that tasks that are so small they don't need sub-tasks could show up as their own rows on the board, though. Right now they get hidden at the bottom unless you create a generic "do it" sub-task.

    2. a general convention is:

      • task = 1 sprint (1 to 4 weeks)
      • subtask = couple of days
      • epic = a set of tasks which spans several sprints
  10. And what to do with Re-open issues from older sprints which already are closed? I would like to add automatically reopen ticket to currently active sprint. Is it possible? 

  11. Is it possible when I edit task and choose field sprint there will only current project sprints?

  12. I'm having a similar issue as Alexander Yuryev.  We have multiple teams using the same JIRA instance, each with their own set of sprints.  It would be great if the other team's sprints didn't appear in the sprint listings, as it has caused some organizational issues in the past when accidently picking a similarly-named sprint from another team's project.

    1. I agree. We have several project teams and some are using similar sprint numbers. Right now our workaround is to put a prefix on the sprint name that corresponds with the project key. I would like to see this feature implemented though so only sprints for that project are available to select. 

  13. Is there an open issue that we could vote on?

    We have a policy that all versions and sprints begin with the project key. Needless to say, the compliance rate is very low.

  14. is it possible to create a sub-task of type bug with a user story?

     

    1. Not that I've seen ... would be very handy, too, so I wouldn't have to raise sub-tasks attached to user stories, then have the first word as "BUG: " in the title. That's the only way I can capture them, at the moment. It's somewhat irritating.

    2. It is possible but it requires some additional setup in JIRA backend by your JIRA administrator:

      1. Go to JIRA Administration -> Issues -> ISSUE TYPES
      2. Choose section ISSUE TYPES - > Sub-Tasks
      3. Add issue type e.g. "Sub-task Bug" and choose appropriate icon
      4. Go to Issue Type Schemes and extend the scheme with the sub-task issue type you created
      5. Make sure that Issue Type Scheme you edited is applied to your project of interest

      We use various sub-task types in my company. It is quite easy and very useful.

      I hope my description will help you to improve your business process.

      Best,

      M

  15. I don't suppose anyone knows if it is possible to get an alert setup to notify certain users when an issue is added to the active/current sprint making the scope of the sprint change?

    Will script runner do the job and if so does anyone know how?