+1 to add time tracking for Kanban board

Would love to have this feature, very surprised it's not there! +2600

+1 We really need to be able to estimate based on days/hours as well. An info on when will that be available?

+9000

+1000

+1

Is there a way to obtain Estimates option under configure board like we get for Classic board?

nicolas.bier - for this feature which has already shipped to Cloud it will assist in communication regarding the Server release.

Kind regards,
Martin
JIRA Software

My guess is that they simply want to track the server release separately in this specific case...it doesn't make any sense otherwise.

@Martin, is this an exceptional situation or does this mean that from now on when people vote for features they will have to tell whether they are Cloud or Server users?

Kanban Backlog for JIRA Software Server will be tracked at https://jira.atlassian.com/browse/JSW-15236 - please add your votes and comments on that issue and continue to watch it for further updates.

Kind regards,
Martin
JIRA Software

The Kanban Backlog feature is now available for JIRA Software Cloud. The release of Kanban Backlog for JIRA Software Server will be scheduled and updates will be posted to this issue. We cannot advise a release number or date for this at this time.

Sub-tasks are supported in the Backlog for the first time. The initial solution will show them by default. We are working on improved cards with functionality to hide/collapse sub-tasks. If you do not want to see sub-tasks in the Backlog then at this point then adding a Quick Filter to hide them is one solution.

The Epics panel is available for the Kanban Backlog but is not enabled by default. This is because the epic issue type has historically been available for display as a card. To change the epics to display in the Epics panel there is an option in the board configuration once the Kanban Backlog is enabled i.e. has a status mapped to it.

The addition of estimates for Kanban is tracked elsewhere at https://jira.atlassian.com/browse/JSW-7265
and there are a number of related Suggestions and improvements for Kanban planning which are tracked separately.

Kind regards,
Martin
JIRA Software

Yes, please!!!!
Having only these two fixed board types SCRUM and KANBAN without any means to configure a mixture seems absolutely weird!
If you want to be religious about either of the two processes, please be, but allow others to configure the tool to their needs. Each of the differences between the boards should be configuration options with the two existing styles being simply two default configurations.

wcoka396006515 - you don't need to activate extra anything to see changes - if you have the Labs feature on you'll get them by default. Recently released changes have been for the onboarding for Kanban backlog and some bugfixes, the next release of changes will include the epic panel and sub-task support.

Kind regards,
Martin
JIRA Software

We're in the final stages of development, there'll be some updates visible for those opted-in to JIRA Software Cloud Labs instances this week.

Hey Martin, any update on this? I see mention that last week there was going to be some update but I cannot see it. Should I activate something?

YAY! any vague estimate for when the feature will be migrated to server instances?

Thanks for watching, commenting and voting on this Suggestion.

We're in the final stages of development, there'll be some updates visible for those opted-in to JIRA Software Cloud Labs instances this week. The team have been working hard on implementing Version and Epic support as well as updating the onboarding experience to be simpler. We're finalising sub-tasks in the backlog and preparing for the feature to exit Labs in the near future.

Kanban Backlog is available in JIRA Software Labs for JIRA Software Cloud as we iterate on the feature. The release of Kanban Backlog for JIRA Software Server will be scheduled once the feature gets fully incorporated into the application.

As clarified in the Current Status field above on 8 August 2016, Kanban Backlog will be scheduled for JIRA Software Server once the JIRA Software Cloud version has been released (out of Labs).

Kind regards,
Martin
JIRA Software

I would love for Atlassian to prove Keith wrong.

On the evidence of this issue though, which I have found very frustrating, I think he may be right.

It should be quite obvious at this point that Atlassian simply does not care about getting this feature to server customers, or about the server product in general. They are of course more than happy to take tens of thousands of dollars over decades from loyal customers, rewrite licensing terms to invalidate perpetual unlimited user contracts, and send you obnoxious "reminder" messages to give them more money for upgrade subscriptions and support that takes 5 days to answer a ticket and only works during AU business hours. But when there's a new feature you actually want, they give priority to their cloud offering to give the higher margin product a competitive advantage and give the big middle finger to their long-standing server customers on whose purchases they built their company. When (if) this finally comes out for server, I give it about 95% odds that all this extra waiting was so they could put it behind yet another addon paywall somehow (Questions for Confluence comes to mind) or create another new, more expensive version of JIRA that you have to buy. But they'll still keep reminding you why you need to give them another several thousand dollars every year for updates.

I've seen failed Kickstarter projects run better than this has been.

When can we expect the JIRA Server version?  I am setting up a scrum board just to get the backlog view and then a Kanban board to enable users to use Kanban, Cloud Labs have been out since Feb?!??!  Please can we get some sort of date?

+1 for Epic Support!

There is mounting frustration on this blog http://blogs.atlassian.com/2016/03/kanban-backlog-jira-software/

You need to actually do something right now: update the community on the status, what you're doing, and when it will be released.

Hi there. I'd like to add another +1 to getting this to JIRA Server. In the original blog post http://blogs.atlassian.com/2016/03/kanban-backlog-jira-software/ there are many comments asking for it as well.

An update would be great. Thanks!

Any update on when we can expect this for SERVER version of Jira? Would be awesome.

@Merv - THANK YOU! I didn't realize that was there.

2) Right-click on the issue and choose "Send to Scheduled".

I've been using the Kanban backlog in Jira Cloud, and it's a big help, but there are still two improvements I'd love to see:

1) Allow me to show other columns such as estimates, story points, labels, etc. so I can use that information to plan what moves out of the backlog.

2) Give me an easy way to move an item out of the backlog without dragging and dropping. In a long backlog, the dragging process is a big pain in the butt as you wait for the page to scroll to the top.

Hey guys,

We have a solution, very similar to KanPlan for JIRA Server(it's called Plangle) , it already has

• Epic support
• Sub-task support

but it needs some modifications to fit your needs perfectly.
Knowing, that Atlassian will possibly release their own solution for server in 6-12 months, it got us thinking whether we should modify our add-on and provide a fast and easy solution for you or not.

Modifying costs us money, therefore we are interested if there's anyone who's willing to pay for this add-on, since they don't want to wait 6-12 months for Atlassian.
To help us decide, please fill out this short form linked below
https://goo.gl/FJDksV

Thanks for your help, looking forward to your feedback,
Aron Boldog
Plangle Product Manager

Alternatively instead of showing the subtasks, a small indicator, next to the spot where story points are displayed in a scrum backlog, would also do the job.

flaimo+jira1939329403 - we're working through sub-task behaviour for the kanban backlog and also epics and versions.
A workaround to help with sub-task visibility meanwhile could be the add them as one of the additional fields on the card.
https://confluence.atlassian.com/display/JIRASOFTWARECLOUD/Customizing+cards#Customizingcards-fieldsAddingfieldstocards

Kind regards,
Martin
JIRA Software

BTW: Why can I set fix-Version on Sub-Tasks, but not plan them separately from theis parent? I cannot even remove the field in the subtasks? That's a nasty inconsistency in the JIRA strategy.

I know, this annoys us too. In our case, QA only tests Standard Issue Types, and not subtasks. Therefore an issue can only go live in a version if all its subtasks are resolved. So we make PRs only for the parent issue, and not for subtasks, as we can only merge the PR when all subtasks are done. Therefore it does not make sense to have a different fix version for subtasks.
I could imagine other workflows, but for our workflow it does not make sense for subtasks having a fix version field. It also does not make sense for Epics for another but similar reason - the epic versions are implicitly given by the versions of its contained issues - in a similar sense, the subtasks versions are implicitly given by their parent issues.

When discussing a Story in the Sprint planning:

• Ranking inside the story to reflect priorities
• Assigning them in a push-situation (expert teams) during the planning meeting (where the focus is on the planning board)
• While planning a story, check with the team if the Sub-Tasks are complete
• Moving into another story to do scoping
• View some of the additional fields (now limited to three) directly on the sub-task
  This was indeed very handy in the classic boards.

I do not vote to have them always visible, but being able to expand a Story with all planning means available (rather than just the summary in the Story detail view) would be indeed useful.

BTW: Why can I set fix-Version on Sub-Tasks, but not plan them separately from theis parent? I cannot even remove the field in the subtasks? That's a nasty inconsistency in the JIRA strategy.

In our case we're actually using several backlogs in the same project. We have mapped our entire product development process, and using a number of different boards to focus on the different parts. We've got one board for product management that have their main backlog + a few steps for discovery, and then move issues to Selected for development. The development team has their own board, and their backlog is the selected for development-column - so it's automatically replenished by the product team. And the product team sometimes need some analyzing / prototyping work or something on an issue, and initially created a subtask for this purpose and put it in the selected for development column. The problem then is that this subtask is invisible in the dev team backlog, so they can't select it for development.

We've worked around this issue by changing any issues that needs to spawn subtasks into epics instead, and create new issues with epic links instead of using subtasks. Works well enough for us, since issues where we need to do this are usually quite big anyway, so an epic makes sense most of the time.

OT: You could also display a field (ScriptRunner calculated/scripted field) that you configure to show number of subtasks, or their issuekeys?

This is not an option, since we already use card colors in another way.

If you have ScriptRunner or JQL tricks, you can easily change the card's color based on this kind of query:
issueFunction not in hasSubtasks()

Or you create a quick filter for the same purpose.

In our case for example the teams do a grooming session one a week, where they decide on how to split the user stories in smaller subtasks (technical and graphical subtasks). Showing the subtasks would make it easier to see where a discussion still needs to take place.
Alternatively instead of showing the subtasks, a small indicator, next to the spot where story points are displayed in a scrum backlog, would also do the job.

Out of curiosity, what kind of operation would you do on sub-tasks if they were visible in the backlog view? Sub-tasks can't be ranked separately from the parent story.

^^^ to add a vote here (not that it actually counts. ) - if subtasks were to be viewable in the backlog, I would like that to be an option, not a default - primarily because of how we can organize stories / sub-tasks / epics. (i.e. I tend to organize a Kanban board similar to how I do Scrum - with a 'story' being the definable and estimate-able unit of work. Sub-tasks might be additional detail, or a ticket that needs to be assigned to someone external to the assignee of the story. Larger groupings of work I put in 'Epics' - and those are the things that need to be broken up over weeks and longer periods of time. That helps ensure - hopefully - that work keeps flowing through the system and large nebulous tickets aren't 'stuck' with no motion on them.)

Yes, viewing sub-tasks would be great.

Apparently subtasks aren't visible in the backlog view? Any idea when that will be fixed? Except from that problem it looks really promising so far!

Three months have passed since the feature was enabled in the cloud. How long do we have to wait until we can activate the lab feature it on our server installations?

As a follow up to my previous comment the plugin has been released

https://marketplace.atlassian.com/plugins/io.extensi.jira.plugin.agileboardfilter/server/overview

@Roger Oberg

I know that may not be an ideal option for Jira users but as an alternative next week we're launching a new plugin that will support full backlog and board filtering

Along to the Quick Filters It will introduce a concept of personalized board and backlog filters, so a kanban board owner will be able to prepare set of complex filters for a planning session without messing around with Quick Filters.

Cheers
Prem

Hi!
While you are working on this, please add the
– Epic Sidebar
– Version Sidebar
to NOT only the backlog view but also the "normal" kanban view, as today in order to filter out these issues, you have to create quick filters on the kanban view in order to quickly filter out epics and/or version on the kanban view.

We’re still improving this feature and getting valuable feedback from those using it in Labs on Cloud. Once it’s ready we’ll be releasing it out of Labs for both Cloud and Server customers. We cannot provide dates unfortunately but please continue to watch this issue for updates.

Kind regards,
Martin
JIRA Software

I see this plugin will come available in the next major release from Jira Server. When will this be?
It would really help us a lot with our project.

Regards,
Dylan

Is there any word on when this will be available in the standalone server version of JIRA (not the cloud hosted one)?

fabian.ehrentraud - no, this will not be available in JIRA 6.
Kind regards,
Martin
JIRA Software

It's happening!

http://blogs.atlassian.com/2016/03/kanban-backlog-jira-software/

@Martin Jopson: It might be early, but when this feature comes to Self Hosted Jira, is there any chance this will come to Jira 6 too?