Currently when our Sprint Completes we have several user stories that are IN PROGRESS or IN CODE REVIEW in our Active Sprint's swimlanes. It could be that the Dev has finished 80-90% of the work done on these tickets but we have to take them to the NEXT SPRINT because they didn't fully meet the definition of DONE. The Burndown chart does not factor this situation as I understand. It only reflects those stories that have moved to the DONE column within a SPRINT. This is an inaccurate representation of a story's burn down for the IN PROGRESS tickets. Can someone kindly suggest me what is the best way to tackle this situation?
I think you have misunderstood what burning down is. It is "counting the issue sizes when they are done". It is nonsense to burn down when a story is not complete. What Jira is doing here is correct, and your process for counting is wrong (not the process itself, but because it's not Scrum, it's wrong for the tool)
I think you may have misunderstood sprints too. When a sprint ends, issues that still have work outstanding on them are supposed to move to the next sprint (or go back into the backlog) because you still need to plan the work on them.
However, you can make Jira handle your process a bit better - put the "in progress" status in the "done" column. Of course, that does mean your process is now marking things done when they might not be, but that is what you're doing already.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events