23ef3e30d63c Thank you! While I understand the original intentions of Jira's implementation of Kanban, I also have a soft spot for the numerous people in the linked threads, and on this ticket, that argue that Story Points are helpful in prioritization and setting expectations at a glance for tickets. e.g., "This is a bigger one, let's knock these small things out first" or "That's a bigger one, that's why it has been in progress for more than a day.".

Which value gets the badge treatment is tied to which is selected as the Estimation tab's "Estimation method" setting for the board, which seems reasonable to me.

With that, I appreciate and support updating this ticket. You may also wish to explicitly include that this should be an option under "View settings", like in Scrum boards and maybe also mention the Estimation tab in the board settings (like mentioned in JSWCLOUD-16957 ).

Regarding the backlog, you are correct. I think I must have hastily selected the "Story Points Estimate" field instead of the "Story Points" field when checking (thanks for your touch-up on JSWCLOUD-17173 btw ).  

Hi 270122f7c34d thanks for your response.

I still can only see a difference in appearance for the Story Points field. The other estimates fields (e.g. Original estimate and Remaining estimate) look the same to me in Scrum and Kanban boards (screenshots below). 

For what it's worth, I was able to find discussion of why Story Points are not fully supported in Kanban, here and here. The UX is inconsistent because these boards' intended functionality is different.

I'd like to update the Summary and Description of this ticket to reflect the changed request as follows but will wait a week before doing so in case anyone disagrees:

Regarding the backlog view - there are two related existing tickets for the Kanban backlog view:
JSWCLOUD-16957 – Add Original Estimate field to Kanban Backlogs without consuming more vertical space
JSWCLOUD-18475 – please include the story points in a badge on the kanban backlog

Similarly, this should be addressed for the backlog view, where Kanban boards cannot display estimate at all

I can't reproduce this - the Kanban backlog card layout functionality seems to be identical to the Kanban board card layout. I've added a screenshot showing Original estimate and Remaining estimate in the Kanban backlog to the description of JSWCLOUD-16957.

23ef3e30d63c, Correct, the points in the "work around" provided uses one of the, already limited, 3 slots for displaying information, and are not shown in the same spot as scrum boards, creating an inconsistent UX. Similarly, this should be addressed for the backlog view, where Kanban boards cannot display estimate at all. If possible, considering the number of votes on this suggestion, I think it would be preferable to update this issue some how, rather than creating a new issue that resets the votes/watchers.

I'd like to check again to see if the watchers of this issue could describe the functionality they are still after in terms of estimates fields on Kanban board cards. As previously discussed, it is now possible to add Original Estimate and Story Points to a card on a Kanban board.

Is the remaining ask for the formatting to be different (i.e for the Story Points field to appear in bubble as on Scrum board cards)? Please let me know, and I can create a feature request that correctly describes the current product functionality.

Hey a5044b6b3064 thanks for the feedback. The only difference I see is how the Story Points field appears on scrum board cards:

Are there other fields where you see a difference between Scrum and Kanban?

I can update the Description of this ticket to ask for the same appearance for Story Points in Kanban, I just want to make sure it reflects the current product behaviour.

It's a poor replacement for what we have on the Scrum board.  it works, but it isn't as tightly integrated.  Also, my customers (aka my tech leads) generally don't like this layout; they want the compact format they get on the Scrum view.

So yeah, it works, but it's less than optimal, it bloats the screen, and it's hard to read.  It's a no for me.

I think the product has changed since this ticket was created. You can add estimates fields like Original Estimate and Story Points to the board card layout of a Kanban issue: https://support.atlassian.com/jira-software-cloud/docs/customize-cards/#Adding-fields-to-cards

Configure Board > Card layout > Kanban board settings:

Does this satisfy the requirements of the watchers of this ticket? Thank you!

This is such a basic planning feature. It's shocking that Atlassian hasn't implemented this. 

Please at least make this an option for those of us who do ScrumBan.

How many years until this is implemented?  Its been on the backburner since 2013 - that is 11 years and counting -  and is a very hard thing to explain to our Jira customers! They take it as an indication of a general lack of responsiveness from Atlassian and are hesitant to go with the tools. Surely this is a matter of cutting and pasting some code from the Scrum backlog implementation.