Fixed Versions - Ability to see scope change and Teams

Question

Im trying to use a Fixed Version for a Release to understand when scope is being added, and removed and which team is working on what

I was told Fixed version will show only Scrum Teams, not Kanban teams.  Is that true?

Any guidance and assistance would be appreciated

Lee

Kit Friend_4u7xxt · Answer

@Lee Street do you mean the Version Report? It would show you changes in scope but not which team is working on what. I always find it's useful to sketch what you're envisaging this would look like and then folks can help offer you some options which might meet that. Typically I'd use something like Plans or just a simple pie chart gadget to show which team owns what.

It's correct that the reporting for Kanban boards is quite limited compared to Scrum boards. Here's a summary from GPT which I think is fairly accurate - related help doc here: https://confluence.atlassian.com/jirakb/reporting-in-jira-461504615.html

Reports for Scrum Boards

Scrum boards focus on sprints, so their reports revolve around tracking sprint progress, velocity, and overall team performance:

* Burndown Chart

* Tracks the amount of work remaining in a sprint.
* Helps teams monitor sprint progress and identify if they’re on track to complete the sprint goal.

* Sprint Report

* Summarizes the work completed and not completed during a sprint.
* Useful for sprint reviews and retrospectives.

* Velocity Chart

* Shows the amount of work completed across past sprints.
* Helps forecast team capacity and plan future sprints.

* Epic Burndown

* Tracks progress on an epic over multiple sprints.
* Useful for understanding whether the epic will be completed on time.

* Release Burndown

* Visualizes progress toward a release goal.
* Tracks the scope and pace of work completion across sprints.

* Version Report

* Tracks progress on a version and estimates completion time based on the current work rate.

Reports for Kanban Boards

Kanban boards emphasize continuous flow, so their reports focus on work item progression and bottlenecks:

* Control Chart

* Displays the cycle time (time taken to complete tasks) for issues.
* Useful for identifying bottlenecks and understanding workflow efficiency.

* Cumulative Flow Diagram

* Visualizes the status of work items (e.g., To Do, In Progress, Done) over time.
* Helps identify workflow bottlenecks and track overall progress.

* Average Age Report

* Shows the average age of unresolved issues in the board.
* Useful for understanding whether work is being completed in a timely manner.

Reports Available to Both Scrum and Kanban Boards

Some reports are available regardless of board type, focusing on project-wide or backlog-related metrics:

* Created vs. Resolved Issues Report

* Compares the number of issues created vs. resolved over a time period.
* Useful for understanding overall project health.

* Resolution Time Report

* Displays the time taken to resolve issues.
* Tracks how quickly teams are addressing work.

* Pie Chart Report

* Shows a breakdown of issues by a selected field (e.g., status, assignee, priority).
* Provides a quick snapshot of distribution.

* User Workload Report

* Displays the distribution of work across team members.
* Helps balance workload.

* Time Tracking Report

* Shows original estimates, time spent, and remaining time for issues.
* Useful for monitoring actual vs. estimated effort.