Managing Issues Across Multiple Sprints

[Neil Regan]

My company is implementing a new system in multiple releases, and have separated the releases as well as some of the different functionality across multiple sprints within the same project. Now that we are moving to our final release, we're working to consolidate any outstanding issues into one sprint, however, are finding it to be a bit labor-intensive to do so. We're needing to move issues from their current sprint into the backlog in order to re-assign.

Is there a faster, more intuitive way to do this, either in existing functionality or planned for future releases? Perhaps the sprint could be assigned in the Issue View itself?

Thanks!

[Scott Theus]

Hi @Neil Regan ,

You could try setting up a Kanban board for your final sprint and use a filter to pull in the remaining issues. If you use a filter to grab every issue for the release that is not DONE your Kanban will allow you to manage them until everything is complete. 

Or...You could also do a Bulk Update to assign the sprint; in Issues and Filters do a search on every issue in the project that is part of the release and is not done, go to the eclipses (...) at the top right and select Bulk Edit. Follow the steps to select and edit all the issues, add the sprint to the correct field, then finish.

-Scott

[Scott Theus]

BTW...if you add the sprint field to the Issue View and field scheme then yes, you can assign the issue to the sprint. You may need to go into the Edit view to add it; the View Issue screen may not show the field if it is empty.

I think the Bulk Edit process will probably work best for you for the current release.