Yep, got one of those how long is a piece of string questions. Am aware there are a lot of variable but here goes...
- Company managed Scrum project that I have admin access to.
- Parallel sprints for company-managed projects is enabled
- There are two teams who share the same backlog, boards use a JQL query that uses a custom field "Delivery Team" that isolates the tickets for each team.
-- Sprint Board 1 JQL: `(project = Foo AND status != Closed AND type != Epic AND "Delivery Team" = "teamA") OR (project = Foo AND status != Closed AND type = Epic) ORDER BY Rank ASC`
-- Sprint Board 2 JQL: `(project = Foo AND status != Closed AND type != Epic AND "Delivery Team" = "teamB") OR (project = Foo AND status != Closed AND type = Epic) ORDER BY Rank ASC`
- For development there is a Scrum board with estimation and time tracking enabled as "Original time estimate"
- The right most column in the Board config has "Dev Done", "Verifying" and "Verified" statuses
- For release there is a kanban board, left most column has "Dev Done", middle has "Verifying" and right has "Verified".
- Release Board JQL: `project = Foo AND status IN ("Dev Done", Done, Verifying, Verified, Closed) AND fixVersion IS NOT EMPTY ORDER BY fixVersion ASC, parent DESC`
- The last status of the workflow (which combines both development board and release board) is "Closed" this status is not mapped to any columns. Tickets get "Closed" when a Jira Version is Released. I've just added "Closed" to the right most column to see if that helps.
There's 2 main issues I have:
1. The sprint report is completely out. in one case (see attached) the report shows only 8 tickets in the sprint, 7 of them added after the sprint start. However, when searching for the sprint in Issue Navigator, e.g. `sprint = xxx` all issues are represented.
2. The Velocity Chart is out also. Almost no time is being indicated as completed even though time has been tracked correctly in Tempo. Doing an issue search shows Time Spent is being calculated correctly.
Questions are:
1. Where do I start debugging?
2. Anyone experienced anything like this before, particularly for the sprint report?





