Then create a board and name the first (!) swimlane "backlog" and the first (!) column also "backlog".

• I guess the goal here would be to make it so there is no need for this?
  • Just use the first column, regardless of name. Or create Backlog column if doesn't exist.
  • Create a swimlane through the plugin, eliminate the prep work for the user.

If you change an existing board, make sure that there are only tasks in the first column in the first swimlane and that there are no tasks in the first column in all other swimlanes.

• Maybe we can figure out a way to just show everything in the column and ignore whatever swimlane it may have been in.
• If we create a swimlane to use as the first swimlane, there will be no need to worry about whether tasks were in the swimlane or not

Most of it works. The only problem is that this way collapsing the columns does not work completely for the main area (columns that are NOT the backlog) and not at all for my new column backlog.

• it all works for me, I say bravo. unless I am missing something. Every column and siwmlane is collapsible.

I'd also add some type of an on/off switch on the board, by doing this, you will be able to go through your own controller where you do all the above, preventing a complete override of existing controller.

Hi all,

It seems that I have a problem with this plugin. I don't have a unique column and swimlanes close to this.

I have the column for each swimlane.

Image

Collapsing the columns itself work, but the width of the columns after collapsing should be minimised. Currently the width stays the same in the backlog-column regardless the column is collapsed or not and it seems that the width is not optimal lowered for the other columns (compared with the original board)

• make of _backlog-column to automatically resize in width after collapsing / uncollapsing AND append the free space to the other columns
• check if column size of other columns is optimised after collapsing them

Configuration

Application version: 1.2.9
PHP version: 7.2.19-0ubuntu0.18.04.1
PHP SAPI: apache2handler
OS version: Linux 4.15.0-51-generic
Database driver: postgres
Database version: 10.8 (Ubuntu 10.8-0ubuntu0.18.04.1)
Browser: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Backlog 1.0.3

There is a big problem with recurrence for any task in project where backlog is enabled.

Step to repeat:

1. Enable backlog for a project
2. Create a task in this project (in any coloum)
3. Add recurrence for that task (with any trigger for recurrence)
4. Activate a recurrence trigger: Move task/close task/ and so on
5. A new task will be create in backlog but will not show in board mode view (but count will be +1) of a project but will show in list - please see an image

Please fix it. Thank a lot for you job

Dear all

We use your plugin with great joy. we wanted to update to the latest version but we had to go back to commit d987c4c because we are getting flooded by notifications (or better 100+ emails / user for each page reload) like "task x has a new position" (roughly translated from german).

The problem does not occur when working in the "traditional" mode without the backlog column.

We "fixed" this issue (while loosing all of our assignments :-/ bc we disabled / enabled the plugin) by revert back to d987c4c.

Honestly we did not find anything "suspicious" within the last few commits which woud explain why this trigger is fired with every task located in the backlog column.

If somebody has a solution for this issue we would appreciate it.

BR wucherfpennig

Added conditional switch in project menu dropdown.

Let us discuss who is allowed to access the menu item to enable/disable backlog column.

If backlog column is enabled, filtering for title does not work. Not for the backlog column nor for the normal columns. Please help!

I use this master and kanboard 1.2.8 and it seems, that the main Backlog column width doesn't take care about collapsed columns in board.

I have main board with 5 columns, from which two are collapsed, but backlog column has width set to 16,6...%, which seems to be result of 100% / (5 + 1). But this simple calculation is bad, if columns are collapsed, backlog column has real width 240px (from min-width), but other not collapsed columns has circa 360px, the two collapsed columns has 28px, by its CSS.

I tried to find way to get collapsed columns, but my knowledge is not enough for this and it seems, that it is handled via JavaScript.

When tying to move the tasks javascript window pops up saying "Access forbidden". If plugin is disabled, then no problem.

• Override of column/index.php and swimlane/table.php

Added conditions:

Hi,

I like the backlog plugin, but want my column to be called "Requests" rather than "Backlog". Would it be possible to add an option to change the name of that column, like I can on any other column on the board?

Thanks

We need to discuss who should have access to the backlog-enable/disable menu item

@vistree 's initial push.

created an extra table (which required a unique swimlane AND a unique column)
https://github.com/vistree/kanboard-backlog

Added Controller, Model, and Hook to Project Menu.
https://github.com/vistree/kanboard-backlog/tree/cree/test_branch

We must discuss who is allowed to access the backlog-enable/disable menu item