Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can i show story points in a JIRA kanban boards

How can i show story points in a JIRA kanban boards

4 answers

1 accepted

3 votes
Answer accepted
Andy Heinzer Atlassian Team Apr 05, 2019

Hi everyone,

There have been several users in the past that have specifically wanted to put estimations on kanban boards.  Ollie's answer has explained there is a way to show that "Story Points" field on a card in a Kanban board, but this isn't the same as being able to estimate issues like you can in a Scrum backlog/board. This isn't something that can be done right now in a Kanban board. There is an open feature request for this in

It's possible that this might come to Jira Software someday in the future. However I don't know if or when that might be.

Estimations are not something Atlassian views as useful in a Kanban project. I would recommend that users that want this, please read our Kanban vs Scrum
page. I think it could help to explain the key differences between these two types of agile methodologies, and in turn perhaps you can see the reasons for why Atlassian built kanban boards in this way. The breakdown chart on that page I think can help clarify why Atlassian has created Kanban and Scrum boards in the way it did. Specifically if you look towards Key metrics and Change philosophy of each methodology:


  • key metric is Velocity.
  • change philosophy is that 'Teams should not make changes during the sprint.' While Kanban change philosophy is 'Change can happen at any time'.


  • key metrics are Lead time, cycle time, WIP
  • change philosophy permits changes at any time

With these concepts in mind, estimations clearly have great value in Scrum, where the speed at which your team works aka velocity is very important but changes are supposed to be limited between sprints.   But since Kanban's change philosophy permits changes at any time, the estimations become extremely difficult to be useful here or provide value when working under this specific methodology.

I hope this helps explain better why Kanban operates in this way.

While watching and voting on the JSWSERVER ticket can help Atlassian prioritize changes and features, in the meantime, there are other 3rd party solutions that might be feasible for some environments. At least one of these I know of that can help achieve this is the Agile Poker plugin

There also could be other solutions in Marketplace for this specific functionality.



With all due respect, Andy, Atlassian's position seems to have a very narrow view of the purpose of story points. Story points have nothing to do with speed. They represent the size of the work, which is comprised of effort, complexity and risk. As pointed out in an excellent article on DZone (, the size of the work is used to help guide prioritization and splitting.

Prioritization is still a thing in Kanban. Constant change merely means constant changes in priority as well. Without the size of the work, prioritization has a serious blind spot in its decision-making.

As for splitting, Kanban boards are fairly useless unless items are moving regularly from one column to another. When an item sits like a lump in the same column for weeks on end, transparency is lost and executives start to question the value of Agile. I've seen teams abandon the use of standups entirely because the status is the same every day. Work that is very large must be split up into smaller tasks that can be tracked. Sometimes that is done with sub-tasks and sometimes it needs to be done at the Story / Task level. Without sizing, that work cannot be done, putting Agile at risk.

Finally, there is the issue of cycle time. I think it should be obvious that the cycle time of a 3-point story is different than the cycle time of an 8-point story. A single cycle time metric that integrates all sizes is horribly inaccurate and cannot be used as a predictor for any given story. Cycle time should be calculated from stories / tasks that have the same size. That would make more sense.

Sizing is important. It's a thing. Kanban needs it. If you don't want to use story points, what do you propose to replace it?

Like # people like this

Fully agreed, Jonathan! Thanks for putting the point with so great and clear aspects of the impacts we have.

I hope Atlassian work on it very soon too!

Like # people like this

Agreed +1 @Jonathan Ginter Thanks for putting such a clear explanation of story point.

Like # people like this

I agree, I think the Atlassian view is narrow and dogmatic in this case. Ironically, we use Kanban boards because of the Scrum principle of no-waste. Creating new sprints is waste, it doesn't add any value. Before we had digital boards, did we screw a new board onto the wall after each sprint? No we didn't. 

Like Aubrey_Yan likes this

Ideology is the end of learning and thus of progress. Jira should ditch the ideology, implement features, and let the community decide how they want to use them.

Like # people like this

i Actually got card layout and success added story point Capture.PNG

But i can not see the field (story point) when i make new isu

Like # people like this

It kind of works: it looks horrible and stupid but we're kind of used to that with Jira

Like # people like this

@Ollie Guan Still it does not show up. Can u please help me with a screenshot of the kanban board where story points is visible

Ollie Guan Community Leader Jul 12, 2018

I have updated the above screenshot

@Ollie Guan okay. Do u have any idea of how we can display story points in releases?? Is this feasible? Both for scrum and kanban boards?

Ollie Guan Community Leader Jul 12, 2018

I have no idea about that case, so I suggest you open another topic to ask this question

0 votes

Agree it's pants that Story Points don't show to the right of the backlog view like in Scrum. One workaround (other than to add an extra line in to show this as per the above) is to create a Quick Filter with the JQL> "Story Points" is EMPTY which will allow you to quickly show which of your tickets are not yet estimated. At least that way you can spot the tickets you need to provide estimates for. It's not great though but thought I'd share it.

Suggest an answer

Log in or Sign up to answer

Community Events

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

Events near you