Moving backlog stories to future release

[Jim Stewart]

We have 33 stories in our backlog. On refining the backlog, we realized that about 25 of them are MVP, the rest for release 2. Is there a way I can flag those 8 R2 stories and put them in their own backlog or parking lot? That way we can focus on only MVP and not worry about those for the immediate future. It also helps in calculating ship date as Jira adds up the backlog time for us and we can easily divide it by velocity. 

[Jose Luis Gaitan · Accepted solution]

Hello, @Jim Stewart Maybe you could mark the issues you don't want to see (using a label or a custom field, for example) and  to create a quick filter for the board, using the label in the search. Doing it, you would only see the issues you need and you could focus the daily work on them.

[Jim Stewart]

Is that the best way? We have a release called MVP that all the issues are in. His thought was we could create an R2 release and move those issues in there. And, I suppose, either they wouldn't show up in the backlog or they wouldn't add to the count. Or are we misunderstanding that feature?

[Jim Stewart]

You know what, I think we can live with having everything in the backlog and just having 'Fix Versions' show us the different releases. I'll close this ticket for now and revisit if it seems to be any issue. Thanks. 

[Bill Sheboy]

Hi @Jim Stewart -- Welcome to the Atlassian Community!

Yes, and to what @Jose Luis Gaitan suggests:

You note forecasting based upon what is in the backlog, perhaps using the built-in reports.  Please check the report you are using to see if it supports use of Quick Filters.  If it does, you can easily ignore the non-MVP issues once you mark the others as MVP.

Kind regards,
Bill