Jira Automation removes the Completed Sprint Issues from Sprint Report

[Nicolae Badareu]

Hello, we have a project with different Sprint Boards since it is a project that has 4 teams involved. 

Whenever the Sprint Ends, the issues in Sprint that are in the last right column are moved to Release Kanban Board. There is an automation for Jira in place that works as: When Sprint Completed, for issues in the state: "X" (that are in the last right column) are transitioned to the Kanban Board in status "Y" (first column in the release board)

The main issue is that the issues automatically moved from the sprint board to kanban board are removed from Sprint Report as being issues removed from Sprint during the Sprint. 
Thank you. 

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Community!

I think there may be a basic misunderstanding of how Jira works here.

You say "the issues in Sprint that are in the last right column are moved to Release Kanban Board" as the main symptom of the problem, but this is not actually an accurate description.

Boards are not containers for issues, they are a view of a set of issues.  Issues do not "move" between boards.  A board selects a set of issues to display.

I think it's worth explaining what your Scrum board is for, rather than try to kludge in a tweak or "fix" that misses the point. 

A scrum board and backlog represent a set of issues that a team are expected to do something about.  The backlog is the list of stuff they've got to look at, and the Scrum board is a view of the stuff they have committed to dealing with in the next timebox (sprint).

You are using the boards to look at issues during part of their lifecycle, but that's not what boards are for.  A board and its backlog looks at the whole lifecycle of an issue.  Your sprint reports reflect this.

There is a simple and quick fix for the problem you present - set up your boards correctly.  Specifically, a Scrum board should include ALL of the lifecycle of an issue.

I suspect your workflow is something like

1. To do -> 2. In development -> 3. ready to test -> 4. in test -> 5. ready to release -> 6. released

And your Scrum board selects for 1, 2 and 3, ignoring 4, 5, and 6.  Change that, the Scrum board needs to include 1 to 6.  Map 3, 4, 5 and 6 into the last column on the board, so that the Scrum team knows they are "done" and can ignore them.

[Nicolae Badareu]

@Nic Brough -Adaptavist- thank you for the quick response. Let me understand it clearly:

So if my scrum board is: To Do->Development->Ready to Test->Waiting for Release (last right column); then whenever i finish the Sprint the Issues have to stop at Waiting for Release Column and not be moved to the Kanban Release Board (which is ready to release, QA->UAT->Done)? 

But since the Sprint is over (Completed Sprint) the Issues have to be presented in the Sprint Report, and it should not matter if I move them after i Complete the Sprint itself? The Report is done at one point of time when the Sprint is Completed and the report should show me the correct data regarding the movement of an issue from column 1 to last column? 
BR. 

[Nic Brough -Adaptavist-]

No, you've missed one of the two main points:  Issues do not move between boards.

>But since the Sprint is over (Completed Sprint) the Issues have to be presented in the Sprint Report, and it should not matter if I move them after i Complete the Sprint itself?

Of course it matters, if you're deselecting an issue from a board, then it is no longer in the sprint, so the sprint report won't report on it.

The reports are not generated and stored at a point in time, they report on the current data.  If you've removed an issue from a sprint (by deselecting it), then the sprint report can't include it anymore.