Jira Automation removes the Completed Sprint Issues from Sprint Report

Nicolae Badareu_ljcw8t

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-

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.