Suraj, even if you mean well in pointing out the uniformity-of-issue concept, that doesn't correlate to actual estimated completion dates. Even if you could have uniformity in sizes, you still would also have to have uniformity in labour. It's just not the real world. Remember; these issues have estimates. The issue here is they aren't visible on boards when they could be.

If Atlassian is saying they don't want them in order to comply with Kanban theory or some nonsense, they need to say that. For the rest of us who use estimates often, revealing them in a view should be straight ahead - especially since it's done in Scrum boards. (Same argument; why do you need an estimate in Scrum, as they all finish at the end of a sprint anyhow… yet Scrum has it.)

So I don't know if you're trolling Suraj, but this ticket is approaching 12 years old. I guess any visibility is helpful, but I agree with Max… that's not how Kanban functions. 

8e2e5b12dfe7 Actually, you seem to have no idea about Kanban, sorry.

Strictly-speaking, Kanban assumes that all your issues are of the SAME SIZE, making sizing using story-points redundant. It is meant to facilitate 'flow'–typically for non-dev teams or for non-dev issues on a dev-ops team. Consider using a scrum board for half your capacity, and kanban boards for the predictable (same-sized) stuff. My two-cents.

What are the updates here?

I've heard from your team that this feature doesn't exist because "estimations are not something Atlassian views as useful in a Kanban project". Your customers are clearly telling you their viewpoint is different and it should be objectively clear that time estimates are critical for improving efficiency.

For example, if I knew I only had 30 minutes between meetings, it would be a much more efficient use of my time to quickly scan next-up tickets and find one that could be completed in that duration rather than click into each one and check their respective story points.

At the very least, your own Scrum, Kanban, or whatever method appears to be failing if a feature as simple as this can't be added within twelve years of being requested. It's a little difficult to trust that you know how to build workflow software if you can't or choose not to deliver here.

Hi, This will be a key feature for most teams- I am shocked it was not already included. I am not sure how long your development processes take but you really should prioritize this ASAP. 

I can't believe that this issue was reported already back in 2013 and you still haven't provided a solution to it 11 years later.
How can you be so ignorant of your user's needs?

 How many years until this is implemented?  Its been on the backburner since 2017 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.

How hard can it be to listen to the community and fix this?

Hey team, this feature would be highly beneficial for all the projects I'm currently involved in, most of which are using the Kanban approach. I'm hopeful that this functionality will be implemented soon. Thank you.

Completely agree with the latest comments, there is a reason 820 people have voted for this, its clearly beneficial to a large community.