jira kanban backlog on server

[BlueHat Dave]

Is there a way to get/imitate the Kanban backlog on the server version of Jira? None of the related questions quite answers this one.

[Jakub Lazinski]

Hi everyone,

Just wanted to make sure you're aware that Kanban backlog is available in JIRA Server since version 7.4.

In the upcoming release of JIRA 7.5 we're going to extend the Kanban backlog functionality to support Versions and Epics panels.

Now you have yet another reason to start planning your next upgrade already now :).
Let me know if you have any questions.

Thanks,
Jakub

[Ben Radlinski]

How do you got it to work in 7.4.2, because it's not working for me? I've followed the instructions, but like the users above, it doesn't show me the Kanban backlog column.

[Steven F Behnke]

Consider asking a NEW question and posting a screenshot.

[Paul Hartness]

I'm running JIRA Software server 7.6 and its not available for me either

[Ingo Mohr]

The Kanban backlog feature is available in JIRA Server 7.4, 7.5 and 7.6.

You just have to turn it on in the board configuration of your board. That's the trick. Go ahead and hit that checkbox. ;)

[Paul Hartness]

I have JIRA Software server 7.6 and there is no checkbox for me to enable the kanban backlog.  Nor any mention of a backlog in the admin settings. The only configuration I can turn on/off is parallel sprints and stick sprint headers.  Any suggestions?

[Ingo Mohr]

Hey Paul,

this might help you out:

https://confluence.atlassian.com/jirasoftwarecloud/configuring-columns-764477997.html#Configuringcolumns-enablingkanbanbacklog

Cheers,

Ingo

[Paul Hartness]

Unfortunately not, my columns section in the board settings does not look like the image given in that link.  It does not mention the kanban backlog or allow me to set it up. :-(

[Ingo Mohr]

Hm. And you have administrator permissions as they say in the howto?

Maybe, the Atlassian support can help.

[Leonard Chew]

I had the same problem as Paul after upgrading from Jira 7.2.1 to Jira 7.7.1:
The Kanban Backlog Panel was not visible in the Columns section of the board configuration.

I checked the Dark Features System Administration Page and I deleted a feature called something like com.atlassian.jira.agile.darkfeature.kanplan.epics.and.versions (I dont remember the exact naming, as I already have deleted it, but the kanban ranking was still missing)
I then added the feature

• com.atlassian.jira.agile.darkfeature.kanplan.enabled

The kanban ranking is now enabled, and I can drag my status into the backlog and activate it, however the epics and versions filters are missing.

My best guess is that the required new "kanplan.epics.and.versions" darkfeature is misspelled and therefore nothing is active by default?
Any suggestions on how to get the epics and versions available too?

[Aleksei Klimkin]

Hasn't Kanban backlog been added to the server version yet?

If not, when is it planned to be launched?

Unfortunately, my company has changed the cloud version of JIRA to the server version, and we were using Kanban backlog feature, but with this transition this functionality seems to be lost for us. Of course this can be done manually, by filtering the needed Issues (with some components in our case) on a status which kept the Issues in the kanban backlog on the cloud version. But this isn't quite satisfying, unfortunately.

[Robert Dzido _Almarise_]

Hi,

You can enable Kanban Backlog using Dark Features:

Go to:

BASE_ULR/secure/SiteDarkFeatures!default.jspa

and enable feature:

com.atlassian.jira.agile.darkfeature.kanplan

Hope it helps :)

Robert

[Benjamin Schwarz]

Dear Robert,

thanks for the nice hacky recommendation—tried that but didn't notice any changes in the board column conf screen. Is there anything else needed, e.g. server restart? Also, we are currently stuck on 7.1.x, is this only supposed to work on 7.3.x?

Many thanks in advance for any thoughts/comments

Ben

[Deyves]

In fact, the correct flag to be added should be this one:

com.atlassian.jira.agile.darkfeature.kanplan.enabled

[BlueHat Dave]

Thank you for the advice.

[Ingo Mohr]

We tried to "emulate" that feature using a Scrum board (which has a backlog feature). We used the following model:

• One running sprint, name "current", end date being somewhere in the future
• One backlog
• Issues are being moved to sprint from top of backlog (e.g. in replenishment meeting)

Problems

• "Done" column gets full very quickly
  
  • Without a quick filter "hide done" you in no time loose grips on the board
  • The only way to get rid of the "Done" issues is to close the sprint and start a new one
    • For this, you first have to add a second sprint because otherwise all "Not-Done" issues fall back to the backlog which makes it hard to start the "same" sprint again in a simple way.
• Release handling is not as easy as on a Kanban board (where you would ship the whole "Done" column as release)
• Always the question: "Why do we have to do Kanban on a Scrum board when there is a Kanban board, as well?"

Eventually, after 6 or 7 weeks, we changed the model to 4-weeks-sprints on a scrum board. The emulation (at least the model described above) didn't feel handy.

[BlueHat Dave]

@Ingo Mohr Thanks for the suggestion.

@Steven Behnke Yeah, that's why I asked if there was a known workaround.

@Mark Bewley Would you be so kind as to enlighten us?

[Ingo Mohr]

I'm also waiting for this one (as it already is available on JIRA Cloud). I found this issue. Maybe that will help for tracking: https://jira.atlassian.com/browse/JSW-15236

[Steven F Behnke]

Kanban backlog hasn't been launched for JIRA server yet...