Expand all | Collapse all

Kanban vertical sorting

  • 1.  Kanban vertical sorting

    Posted 09-05-2018 14:48
    A question regarding the sorting.

    So Kanbans automatically change the grouping "based on" field value when dragging "across" the groups.  

    Will there ever be an option to have the fields change on a vertical drag? so for example if the sorting order is from 1-6, by dragging card 6 to the position of 1, the fields will swap values and changes are made?

    I find this particularly useful in a scheduling type environment for dragging and sorting Jobs etc.  an example would be to group by technician then have the sorting order be on scheduled time etc.  

  • 2.  RE: Kanban vertical sorting

    Posted 09-05-2018 15:18
    Re: "will there ever"

    The future is now. Is that soon enough for you?

    Go to the table
    Advanced Properties
    Go way down to the bottom and the option switch to enable that is there.

  • 3.  RE: Kanban vertical sorting

    Posted 09-05-2018 17:36
    Hi Geoffrey,

    Mark is correct and that functionality actually has been added to our Kanban reports based on the feedback of our users who had the same needs as you. We have a help topic that goes into that feature in more detail that you can find here">https://help.quickbase.com/user-assistance/kanban_manual_ordering.html">here. Hopefully that can help to answer any questions you have on manual sort for Kanban reports. 

  • 4.  RE: Kanban vertical sorting

    Posted 09-05-2018 18:16
    yes, so this works on face value,  but the actual field value that it is sorted on doesn't change.  this is taken directly from that same help document:

    "Note: This only sets an initial order for your Kanban reports. Users can then reorder cards by dragging them on a report. This does not affect the values of the field chosen as the initial order field."

    So where is the future? :)

  • 5.  RE: Kanban vertical sorting

    Posted 09-05-2018 18:26
    Right. It does not edit field values to change a visible sort order field. The sequence is only maintained in the Kanban format report, not on say a table report.

  • 6.  RE: Kanban vertical sorting

    Posted 09-05-2018 19:00
    When you engage manual sort order it still puts information into order on the Kanban report based on the sort order of the original field being used (For example if it was in order by Date Created) but then once manual sort is enabled any records that are specifically pulled out of order, in your example record six being pulled to be the 1st in priority will now going forward be in place as the first record in that order while the other records will continue to use the previous sort until they are pulled manually into a different sort. The previous sort order exists as a stand in until you chose to take action to change the records sort order but it wouldn't change the Date Created on that record just the records place on your Kanban report. 

  • 7.  RE: Kanban vertical sorting

    Posted 02-07-2019 17:55
    I want to implement an Agile type of methodology, whereby my Sprint team can moves items between columns to show the Status - this works well between columns, and if I move an item, the Status changes.
    However, I also want to have my Product Owner vertically sort the Items with the "Prioritizing" Status column. I have a Priority field on the Item, but this doesn't change if I vertically move the Items within this column. How can I save this Prioritization, so that the rest of the team can see the Priorities set by the Product Owner?

  • 8.  RE: Kanban vertical sorting

    Posted 02-07-2019 19:53
    In the Advanced Settings for the table there is an option to enable manual sorting. But that then would be available to all users. So it may be a problem in your use case.

  • 9.  RE: Kanban vertical sorting

    Posted 02-07-2019 22:37
    You can have more than one Kanban report on a table.

    On the team's report changing columns changes the Status field
    On the owner's report changing columns changes the priority field. 
    Then set the team's report would sort by priority

  • 10.  RE: Kanban vertical sorting

    Posted 02-08-2019 19:35
    The direct answer is, right now you cannot do this. The Kanban report can only exist on one bucketing variable. The vertical sorting is a kind of epi-value that exists only for the purposes of sorting that Kanban report, and is persistent but not tracked or evident anywhere else in your app's universe.

    Here's one way of addressing this. Create values in your Status field for 'update priority' for each priority ranking you want to be able to reassign your jobs to, and have them display on your Kanban. Set automations to fire when the Status value is changed to those values to change its Priority (and reset its Status as well)

    It's slightly awkward to use, as you might expect. But it works! Here's a quick demo:

    So we've got a two variable workspace: Status and Priority. The Kanban groups by Status and sorts by Priority. Here are the multiple choice settings for Priority and Status:

    Here's the automation (I set up just one, for 'MAKE HIGHEST')



    It works perfectly. Just the view doesn't refresh automatically.

    Drag your Kanban card from its status column to the "change priority" column (I only drew up one for the demo but it can be as detailed as you want/have space for); the automation changes the priority to the one you've linked to that status category and then re-sets the status (I had it re-set to 'queued' but you could create a custom status or set it to a particular one, or or or..)

    So it's a hack to be able to update your Kanban sort field even though the report can't directly manage that field for you. You just have to manually do one of two things: refresh the report, or drag the card to your preferred Status column (this actually works fairly well, and makes intuitive sense to me - it's like those old 'factory ball' Flash games - use the 'CHANGE PRIORITY TO..' column to 'paint' your job with the priority you want, then when you put it in its proper Status column you'll have re-sorted the priority permanently).

  • 11.  RE: Kanban vertical sorting

    Posted 02-08-2019 19:39
    Extension to the use case where some roles should only be able to see the native status values and some should have access to the columns that change prioritization should be fairly trivial; create one Kanban with all the Status columns and one without the 'MAKE ... PRIORITY' columns and permission those reports based on role.

  • 12.  RE: Kanban vertical sorting

    Posted 21 days ago
    Edited by Johnny Niumata 21 days ago
    I know this is an old post, but since I found a new solution I thought I would share.

    when you enable sortable kanban on a table, a hidden field is added to that table. The hidden field is called "KanbanPriorityOrder", and the order is saved in this hidden field as a number.
    Unfortunately since it is hidden, you cannot order reports on this field, so we have to copy it to a newly created field.

    my solution requires 2 main steps.
    1. adding a new numeric field to a table (eg. kanban-sort-copy) , (I manually set all existing records to value of 1000)
    2. using a webhook to copy the kanban sorting order into this field, whenever sort order is changed.

    I will only talk about step 2

    here is my webhook (API_EditRecord)
    <rid>[Record ID#]</rid>
    <field fid="77">[KanbanPriorityOrder]</field>

    I manually typed in the [KanbanPriorityOrder] after I found it's name using the restful API (it does not show up in the dropdown of fields)
    field 77 is my new numeric field that I created.
    this webhook looks for all updated records and then copies the kanbanPriorityOrder to the new field.

    Now I just sort reports using my new field.
    so far it is working well for me.

    Johnny Niumata

  • 13.  RE: Kanban vertical sorting

    Posted 20 days ago
    Thx for posting this.  I did not test it all out,  but I did take note of the fid of my highest numbered field, then enabled Kanban in Advanced Properties and then added another field.   The fid of the new field "skipped" a number, as your discovery would suggest it would as the new hidden field took up the next fid.

    Also, rather than a webhook, I simply created a formula numeric field called [Kanban Priority Order mirror] with the formula


    Although the formula editor complained in yellow, in fact the field did save without errors and worked just fine on a table report  as a column or a sort field.  So no Webhook is required.

    Thx for the tip.

    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach

  • 14.  RE: Kanban vertical sorting

    Posted 20 days ago
    good idea to use formula numeric.
    I'm new to quickbase, so not sure when to use the correct method.
    is there a way to change formula so that if it is empty or zero to set the value to a high number so that non-sorted items are lower in the order?

    Johnny Niumata

  • 15.  RE: Kanban vertical sorting

    Posted 20 days ago
    I don't think it can be empty or zero.  I believe that when you first enable the Kanban on he Advanced Properties of the table it orders them by the default sort field - ie the sort set on the default report which might just be by highest date modified first, if it was not changed.

    When you enable the feature there is a pop up message saying to "wait a sec while I do some work".  I'm guessing that  it is then going ahead to create that new field and then assigning a value to all existing records.

    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach

  • 16.  RE: Kanban vertical sorting

    Posted 20 days ago
    I just tested adding in more records and it automatically created the sort order number by incrementing to the previous sort order number within that kanban column (in my case "work ticket status" is the column). 

    here is a response from the table in JSON
    { "data": [ { "25": { "value": "WC1.01" }, "72": { "value": "Not Started" }, "75": { "value": 19.9 } }, { "25": { "value": "CAS1.01" }, "72": { "value": "Casting and Shipping" }, "75": { "value": 30 } }, { "25": { "value": "JAM1R.01" }, "72": { "value": "Mold Prep" }, "75": { "value": 69.701 } }, { "25": { "value": "SSK2.01" }, "72": { "value": "Mold Dept" }, "75": { "value": 60.2 } }, { "25": { "value": "SSK2.02" }, "72": { "value": "Mold Dept" }, "75": { "value": 60.1 } }, { "25": { "value": "SSK2.03" }, "72": { "value": "Mold Prep" }, "75": { "value": 69.60000000000002 } }, { "25": { "value": "UB1.0" }, "72": { "value": "Not Started" }, "75": { "value": 21 } }, { "25": { "value": "UB2.0" }, "72": { "value": "Mold Prep" }, "75": { "value": 69.50000000000003 } }, { "25": { "value": "JAM1.01" }, "72": { "value": "Not Started" }, "75": { "value": 90 } }, { "25": { "value": "KS1.1" }, "72": { "value": "Not Started" }, "75": { "value": 100 } }, { "25": { "value": "PAN13.1" }, "72": { "value": "Not Started" }, "75": { "value": 110 } } ], "fields": [ { "id": 25, "label": "Part number variant", "type": "text" }, { "id": 72, "label": "Work Ticket Status", "type": "text-multiple-choice" }, { "id": 75, "label": "KanbanPriorityOrder", "type": "numeric" } ], "metadata": { "numFields": 3, "numRecords": 11, "skip": 0, "totalRecords": 11 } }​

    Johnny Niumata