Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

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).

(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.

To add an issue to a sprint,

  1. Log in to JIRA.

  2. Click the Agile link's down-arrow in the top navigation bar, then select your preferred board from the resulting dropdown menu.

  3. Your board will be displayed. Click 'Plan'.
  4. 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.

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

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

 

 

Related pages:

 

 

 

 

46 Comments

  1. mkumm

    Adding an issue to current sprint is not working (Mac/Chrome). Dragging an issue to the active sprint on the top of list does not add the issue to the current sprint. I do not see an alternative way to add issue to the current sprint

    1. Rosie Jameson [Atlassian]

      Hi, just checking that you are using GreenHopper 5.9.1 or later?

      Many thanks,
      Rosie

  2. Sam Hutchinson

    How do you delete an issue from a sprint, by mistake i dragged the wrong issues into the sprint but now I can;t get it out of there

    1. Gary Gilbreath

      I have this problem too, but I did find a way to do it. First make sure you've configured the issue screen to have the "Sprint" field on it (Administration/Issues/Screens.../Configure/Add Field). For me I'm using the Default Screen, so I just added it to the default screen. Now open the issue you want to remove from the sprint and navigate down to the Sprint field. There should be a number in the field. Blank out the whole field and hit the Update button. That issue and any sub-tasks associated with it should now be removed from the sprint and back in the backlog. This appears to be an alternative way to add issues to a sprint too, though the drag and drop is a lot easier.

      It would sure be nice if there were a less painful way to remove issues from a sprint.

      I'd also like a way to remove the whole sprint, to make it as though it had never existed.

    2. Rosie Jameson [Atlassian]

      As of GreenHopper 5.9.8, you can remove an issue from a sprint..

       

  3. Anonymous

    Hi

    i want to add issues which are currently Status = Resolved, Resolution = Fixed. However, filter returns these issiues as a result, these issues are not listed in Backlog screen.

    Btw, Status = Resolved, Resolution = Fixed means code is generated unit test is made and now functinality or work is avaiable for testing. If tests are succesfull, we close the issue.

    1. Anonymous

      Curious if you ever found a way to do this - we have several cases why this would be necessary and currently prevents QA from utilizing GreenHopper.

    2. Joe Ramseyer

      I'm looking to do the same thing here without the tedious work around of opening the item, putting it on the planning board and then resolving it again.  I have over a 100 closed/resolved/fixed issues that I want to move to the sprint planning board.  Anyone figured out how to do this?

  4. Anonymous

    Please add the following sentence or something similar at the end of "Drag the issue onto the active sprint (the 'Sprint in progress', shown at the top of the page)."

    " and not above the sprint marker"

    I got confused on how to add a story to a started sprint, as in planning mode you drag issues above the spring marker (or move the marker), but when adding to an already started sprint one must drop the task onto a field "Sprint in progress".

    Maybe a picture would be in order.

    1. Rosie Jameson [Atlassian]

      This page has now been updated as the UI has changed for GreenHopper 6.0

      Thanks for your feedback.

       

  5. Tanny

    Hi Rosie,

    From the image that you have attached, i can see 3 sprints, 'Sprint 4 Bolognese','Upcoming Sprint 1', 'Upcoming Sprint 2'. I have been searching an answer to display the previous sprints in plan board. Can you please explain it to me the way you have done it?

    Regards,

     Tanveer

    1. Tanny

      ohhh... i just upgraded greenhopper and now I am able to add different sprints to my product catalog. thanks (smile)

  6. ben ishiyama-levy

    Would be great to add a JQL hook for 'upcoming sprints' as for being able to filtering them out from backlogs on other boards.

    Also, changing the sprint name fields for upcoming sprints would also be mint, along with punching in the start / end dates

    1. Rosie Jameson [Atlassian]

      Hi Ben

      Re JQL, you may like to watch/vote/comment on https://jira.atlassian.com/browse/GHS-5773

      And you'll be pleased to hear that we have just met your second request in GreenHopper 6.0.2.

      Cheers,
      Rosie

       

  7. Parker Fleming

    Is there a way to add issues to a sprint when creating the ticket? We often find bugs that we want to add to the sprint as we log them, and it would be nice if we could add it to a sprint via the create/edit issue screen.

    1. Oliver Young

      This has been a major issue for my dev team as well. We had been using the Fix Version to do this for the Classic boards. There has to be some way to do this that does not require going all the way into the planning board.

    2. Daniel Goldman

      I'd like to add my vote to this as well. In prior versions of Greenhopper allowed me to add a ticket to a sprint from the ticket page. I would often go though ticket by ticket (via a search or through other means) and manually add them to sprints using the 'Fix Version' field.

      This is keeping me from switching out of the classic view.

      1. Anonymous

        Any news on this one?

        Same problem for us

    3. Marcel Kleinlütke

      I only can guess. Why I only guess? Because it works with my setup but I cannot readjust it and hope it is just a time gap.

      What have I done:
      I added a greenhopper sprint field and set a default value (in my case it was the "1" because that was the value of my active Sprint) additionally I set a PostFunction where the value of this field was set to 1 too
      One of these solutions has worked.... I guess

      1. Rosie Jameson [Atlassian]

        Hi, you may like to watch/vote/comment on GHS-6866 - Getting issue details... STATUS

  8. Anonymous

    Is there a way to reorganize the sprints after you've added them? I have three upcoming sprints and I need to place the last sprint on top (as I've had to add some requirements to the project). I can't find a way to move the sprint up a couple of steps.

    Is it even possible?

  9. ray

    I cannot see my story on the Plan board to add it to the sprint. What's the possible reason of this? Thanks.

     

  10. Anonymous

    What's the associated permission with adding a ticket (scheduling?) and also removing a ticket from an active sprint?

  11. Anonymous

    I'd like a way to automatically add a newly created issue to the current sprint.  Is there a way to do this? The extra step of having to drag the issue up to the sprint from the backlog is cumbersome.

    1. François Boissonneault

      Same here : we are fixing bugs during the sprint, to provide a "ready to ship" version by end of the sprint. It seems odd that it doesn't allow us to do so automatically during a sprint. #heavyForUser

      1. Anonymous

        For fixing defects within the sprint, we created a new subtask type 'defect', so we can associate a defect raised against a story in the sprint by adding a subtask on the story of type 'defect'. So when all the defects are cleared by dev, then it is "ready to ship"

  12. Anonymous

    Is there a way to add sub tasks to separate sprints ? (e.g. Task 1 has Sub Task A and B, Sub Task A is in Sprint 1 and Sub Task B is in Sprint 2) I can only put a task (and all of its subtasks) in any one sprint. Thanks.

    1. Anonymous

      +1 

      Going nuts trying to figure out how to do this. Hard to believe it can't be done.

  13. Greg Stewart

    Please add another way to add issues to an active sprint. Dragging is ok if you don't have many issues but we typically have many hundreds and to drag from the bottom to the top takes way too much time. Suggest adding dropdown menu item in the issue preview that allows adding to a sprint.

    1. Rosie Jameson [Atlassian]

      You may like to vote/comment on GHS-5656 - Getting issue details... STATUS

  14. Dave Tollefson

    For those wanting to be able to create issues directly into the current sprint, I believe this is the relevant story.  It needs votes.

    GHS-6455 As a user I want to easily add new issues to the current sprint from the RapidBoards

  15. John Bailey

    My team is looking to add cards to a Future Sprint not an Active Sprint. Basically, the idea of adding cards to a Sprint by dragging-and-dropping is nice, but we need ways to add the card to a Sprint within the edit mode of a Card. Again, this is not about Active Sprint like many are requesting. This is targeted at Future Sprints.

    1. Rosie Jameson [Atlassian]

      You may like to comment on this issue to expand its scope to include Edit mode: GHS-6303 - Getting issue details... STATUS

  16. Sandra Axelsdóttir [Tempo]

    Is it possible to restrict access to adding issues to an active sprint? I would like the Product Owner to be the only one who can add issues to a sprint when it's active.

    1. Rosie Jameson [Atlassian]

      Not at this time. You may like to raise a feature request at https://jira.atlassian.com/browse/GHS

      1. Anonymous

        Isn't this what is captured in:

        https://jira.atlassian.com/browse/GHS-5977

        or https://jira.atlassian.com/browse/GHS-6387

         

         

        1. Sandra Axelsdóttir [Tempo]

          This Issue seems to cover what I mean - GHS-5977 - Thanks

  17. Christopher Warin

    Is there a way to create a sprint from items that are not in the backlog?

    For example we have 10 items in the fixed version 1.0 and want to create 2 sprints out of this.

  18. s s

    When I right click on items in my backlog, I don't get the option to move to a sprint. I get only browser options; no JIRA options. Why is this?

    1. s s

      Nevermind, I just realized that was a 6.1.2 addition. Currently on 6.1.1. Updating should resolve it.

      1. Michael Bennette

        Thanks for adding your second note. Helped me after I've been scratching my head why I could not see the right click options. Also on 6.1.1.

  19. Mikkel Kragelund Nielsen

    What is the idea behind not being able to add sub-tasks individualy to a sprint. This limitation Means that a feature/bug always have to be done within a single sprint. Or we have to start it 1 one sprint and then move it to the next sprint.

    But this approch gives a incorrect picture of how god our team is at setting the right commitment. The feature might be 80% done once the sprint ends. But 100% of the feature is marked as "Issues Not Completed".

    1. Tom Kotecki

      Hi Mikkel,

      This is deliberate. Since what you're trying to accomplish at the end of each sprint is shipping as much customer value as possible, your aim should be to bring in stories of appropriate size so they can actually be completed in the time frame of a sprint. We don't encourage adding sub-tasks individually to the sprint, since completing a subtask by itself brings no customer value (it's inherently not shippable without completing the story).

      Note that this is different from technical tasks or bugs, which don't have the parent-child relationship with stories.

      You can read more about estimation and reasons why we don't count 80% complete stories towards your velocity here.

      Cheers

      Tom Kotecki

      Product Manager, GreenHopper

  20. John Burns

    I feel that the "Edit Issues" permission to add an issue to a sprint is too liberal. Currently, we have people who can add issues to a sprint (who shouldn't), but they can't change the ranking (because they don't have "Schedule Issues" permission). Greenhopper will display an error when they drag an issue into an active sprint saying they can't change the rank, but it will still add the issue to the sprint.

    I think adding issues to a sprint should be tied to "Schedule Issues", or still tied to "Edit Issues", but add an additional check to make sure they can change the rank before adding to a sprint..

  21. Aaron Carter

    Why aren't the Subtask's created under a Epic not showing in the Agile Scum Board Backlog? If I create an issue and associate it with a task it will show up in the back log, however sub task's of the epic will not show up in the product backlog.  This wasn't an issue in the Classic planning board. 

  22. Michael Hill

    How can you add a new project to an active sprint?



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.