Particular Issuetypes (tickets NOT Done) are not rolling to the next sprint
Asked by Wendy Filip:

We've been noticing that particular issue types (ticket types) are not rolling from sprint to sprint. Our "Test Activity" and "Enabler" ticket types do not roll. They stay in the prior sprint. Our other issue types (like Stories, Defects, Tasks, etc.) roll to the next sprint just fine.

I know that tickets don't roll that are in a "Done" status (like our Closed, etc.) - but when we specify that we want open/incomplete tickets to roll to the next sprint (select it during the roll process) - we expect that every ticket type should roll.

These ticket types have a status of Open or In Progress. These status values are defined in our Columns for the Project (i.e., Open is in "To Do" and "In Progress" is in "In Progress".

It seems rather coincidental to me that it's just particular ticket types that aren't rolling (our Enabler and Test Activity ticket types). That leads me to believe the issue is in some kind of Administrator set up of those ticket types.... or it's a bug in JIRA.

Has anyone had this issue?


Answers:
author: Wendy Filip
body: ![Project Columns.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/337417i709525BD976049E3/image-size/large?v=v2&px=999 "Project Columns.jpg")

Here's the column definitions. The Enabler and Test Activity ticket types had status Open (In To Do) or In Progress (in In Progress). None were in a "Done" status.


author: Joe Pitt
body: Do they have a resolution value?

comments: author: Wendy Filip
body: They have "Unresolved" in their Resolution value (the ones that didn't roll).


author: Trudy Claspill
body: Hello [@Wendy Filip](/t5/user/viewprofilepage/user-id/4377292)

What is the filter for this board? Is it limited to a single project?

Can you show us the Columns/Status mapping for the board?

comments: author: Wendy Filip
body: I copied in a screen shot of the Column/Status values.


author: Trudy Claspill
body: What is the filter for this board? Is it limited to a single project or pulling from multiple projects?

Are the issue types that are not moving to the next sprint in the same project as the ones that do, or in a different project?

> They have "Unresolved" in their Resolution value (the ones that didn't roll).

When you look at the details view of the issues that did not move does it actually say "Unresolved" next to the Status pull down, or is nothing displayed next to the Status pull down?


author: Wendy Filip
body: The board pulls from one project - and yes - the other tickets not in a "Done" status are rolling into the next sprint. It is only the ticket Type that seems to be the issue. These tickets are all in the same project. Our Enabler and Test Activity ticket types are the ones not rolling. The Story, Defect, etc. tickets roll fine. All these tickets (as well as most that rolled fine) have Unresolved in their Resolution until they are closed. ![2024-07-24_07-13-32.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/337612iA98A03286B92C6FD/image-size/large?v=v2&px=999 "2024-07-24_07-13-32.jpg")


author: Trudy Claspill
body: Forgive my last question. That was based on me thinking you are using Jira Cloud, but I see from your tags you are using Jira Data Center.

What version of Jira Data Center are you using?

Summarizing the facts that have been established:

- Some, but not all, incomplete issues move to the next sprint.

- The issues that don't move are all issues of two specific issue types, and no issues of those types move.

- Those issues are in the same project as the issues that do move.

- Those issues are in Statuses that are mapped to columns of the board, and the statuses are not mapped to the right-most column, and are not part of the Done Status Category.

- Those issues show "Unresolved" for the Resolution.

Here are a couple of additional questions.

1. You said the issues don't get added to the next sprint. Do they move into the Backlog?

2. In the Sprint Report for the sprint you have completed, in which section are the issues of those types listed?


author: Wendy Filip
body: Hi -

We are running version v9.12.7.

1. They stay in the prior sprint. It's as if they don't get pulled for any roll at all (into the backlog or into the next sprint) - as if somehow those ticket types are ignored.
2. They appear in "Issues Not Completed" in the Sprint Report for the prior sprint.


author: Trudy Claspill
body: This is a little confusing.

If the issues are considered incomplete, then they should appear on the Backlog screen for the board, either in the list of issues under the Backlog heading, or within one of the sprints shown on the Backlog board.

Are you saying that the issues that didn't more are no longer displayed on the Backlog screen at all?


author: Wendy Filip
body: I'd have to check that at the next sprint roll. Since I have a short time between rolling the sprint and the first of my sprint review/planning meetings (I'm a scrum master) - I have been doing a bulk update to sprint on these tickets prior to the meeting.

So the next time I roll - I'll first see if I see the tickets in the backlog on the scrum board BEFORE I bulk update the sprints on them. I do know they keep the prior sprint on the sprint field when they don't roll.


author: Trudy Claspill
body: Issues retain all the Sprints to which they have been assigned unless they are actually removed from the sprint.

The Sprint field is designed to hold a list of Sprints; all the sprints the issue was assigned to but in which it was not completed, plus the active (or future) sprint to which it is currently assigned.

At the end of the sprint when you Complete it, the incomplete issues should continue to show that sprint in their sprint field. Without that association of historic sprints to issues your Sprint Reports would change. The historic information is used in the sprint reports to show at the end of the sprint the issues that were incomplete. If you remove the association between the historic sprint and the incomplete issue, then the sprint report will change to show a reduction in the burndown due to the issue removal.


author: Wendy Filip
body: Right now - the only way to get Enablers and Test Activity tickets into the next sprint (these often are worked on over several sprints) - I have to do a bulk update - since the sprint roll doesn't work. It may impact some older history reports - but that's not my main concern. My concern is that I need to see those tickets in the current sprint after the roll.


author: Wendy Filip
body: Adding some additional info.....

Here's the Workflow for our Enabler and Test Activity (second) ticket types: ![Enabler Workflow.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/337404i11D70196FE1C5B70/image-size/large?v=v2&px=999 "Enabler Workflow.jpg")![Test Activity Workflow.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/337406i25322AB22590B331/image-size/large?v=v2&px=999 "Test Activity Workflow.jpg")


Tags: data-center

jira-data-center

sprint