I wonder what is the best way to manage the ticket in JIRA which has to go through kanban flow and multiple sprints before the closure.
I wonder how to mange definition of done after each of those iterations and once DoD is met on former cycle ticket to be moved to next cycle.
Welcome to the Atlassian Community!
The best way to manage an issue that has to go through multiple sprints is to not do it that way. An issue should be completed within a single sprint.
If you think you have issues that will need to be done across many sprints, then you are not devolving your stories enough. The whole point of a sprint is that you are committing to completing the stories you choose to bring into it in that one sprint. If an issue rolls over into another sprint, your team has failed, and it should provoke a discussion about why you failed and how you can do better next time.
Thank you Nic,
I would like to highlight though, question was not about the scrum but rather about the tool.
If JIRA can not do it, that is fine, if there is a way though i would like to know it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jira can do it, but it won't be Scrum or Kanban, it will not be pretty, and you're going to have massive problems doing it and reporting on it. I'm afraid your process is broken.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.