I frequently work with Scrum teams where we use a Scrum board to track the work done in Scrum teams in a Sprint and also a Kanban board to track the flow of work upstream (before it arrives at the Scrum team) and downstream (from meeting the Scrum team's definition of done to being released).
In particular there are issues specifically to do with the "Status Category" and the "Resolution" field when tracking issues in a Sprint and then through downstream activities in a higher-level Kanban board.
In brief, the rightmost state in the Scrum board flow for a Sprint will always have a Status Category of Done. The Status Category affects things like Version Details, Sprint Health Gadget and the Epic progress bar. Assume that there are two further downstream states in the Kanban Board, after an issue has reached the Scrum Teams definition of Done. The first downstream state in the Kanban board will have a Status Category of "In Progress" because it is not the rightmost state in that Kanban Board. So as the issue moves from the last state in the Scrum Board to the next downstream state in the Kanban Board, things like the Version Details, Sprint Health Gadget and the Epic progress bar will appear to go backwards as things that were considered Done are now In Progress.
There is a similar issue with the Resolution field if it is set in the final state of the Scrum Board but not in the first downstream state in the Kanban Board. This affects whether an issue has a strikethrough on boards, "Created vs resolved" reports and some System filters such as "Open Issues" where again things will appear to have gone from closed/resolved back to Open.
How are other people managing this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.