Getting Started

Expand all | Collapse all

KANBAN

  • 1.  KANBAN

    Posted 21 days ago
    I have a Kanban report showing associates by Team Number. In each individual record I have their immediate supervisor as well as the next tiered supervisor. 
    The question is. If I move an associate from Team 1 (with its supervisors) to Team 2 (with a different set) is there anyway to automatically change the managers without going into the record and manually updating it?

    ------------------------------
    Hans Hamm
    ------------------------------


  • 2.  RE: KANBAN

    Posted 20 days ago
    Hi Hans,

    One of the app builds that is used for this kind of workflow is to create a parent table to your current table that is your Team table. It would contain information like the Team Number, Supervisors, etc. You would then set your relationship up so that when someone picks a Team Number they are actually pulling down all the information for that team down from the parent table. Then if you changed the Team a user is associated with it pulls down the correct Supervisors and other team specific information instead of having to manually change any of your fields that holds that information for them. It can take a little set up to get in place but then it allows you that ability to simplify updating that information (especially in the future if you for example had a Supervisor leave and needed to suddenly find everyone assigned to them and update you would instead update that one team record).

    ------------------------------
    Evan Martinez
    ------------------------------



  • 3.  RE: KANBAN

    Posted 20 days ago
    Evan,
    So, I built a Team table and related it back to the associate table..
    That is when I realized (did not know this) that the only fields in the Kanban are multi-choice fields.
    I am not sure I follow how to get the Team Number to work. If I use it in the relationship it is no longer available as field the chart can be based upon... Can you explain a little bit more of what I am missing??

    ------------------------------
    Hans Hamm
    ------------------------------



  • 4.  RE: KANBAN

    Posted 19 days ago
    Hi Hans,

    Do you have a large number of teams currently or only a small number of teams? I didn't realize you were using the Team Number field as the field in your Kanban report as the sort field. Cause one option would be to leave it on the multiple choice manual field and set up a Pipeline to change their related Team (and the related team info like supervisor, etc.) when the team changes but that is a lot easier with a small number of teams and harder with a large number of teams. This would allow you to keep the kanban behavior and then in the background the Pipeline would help reset their associated supervisors, etc.

    ------------------------------
    Evan Martinez
    ------------------------------



  • 5.  RE: KANBAN

    Posted 4 days ago
    Evan,
    Been a busy week, or so... at this point we have 24 teams. I have not done any work with pipelines..
    Can you provide the general idea of what you are suggesting?
    I thank you!

    ------------------------------
    Hans Hamm
    ------------------------------



  • 6.  RE: KANBAN

    Posted 4 days ago
    FYI, the Max # of columns is 15.  That might include the blank column.


    https://help.quickbase.com/user-assistance/quickbase_limits.html

    Maximum number of columns in a Kanban report=15

    Maximum number of cards (records) per column in a Kanban report=100

    https://quickbase.uservoice.com/forums/111823/suggestions/35052007





    ------------------------------
    Mark Shnier (YQC)
    mark.shnier@gmail.com
    ------------------------------



  • 7.  RE: KANBAN

    Posted 3 days ago
    Hi Hans,

    That could be a little trickier since you do have that many teams and that is going to exceed the groupings available in a Kanban report as Mark noted in his response. At that point you would possibly be better served by a Grid Edit report where users could move projects from team to team via the relationship field, it is a little less visually pleasing but would allow you to have all the options represented instead of being limited by the 15 columns as they are limited today. 

    For a smaller number of teams you would have set up a Pipeline that was set to trigger each time the value in the Team field was changed and you could have set up conditions so that for each Team the Related Team field would be changed to the correct team. Essentially setting it so that if the Team Field is changed to Design for example Change the Related Team field to the Design Team's record. You can see an example of how we set up a Pipeline to target the record that triggered the Pipeline in this example article.

    ------------------------------
    Evan Martinez
    ------------------------------



  • 8.  RE: KANBAN

    Posted 5 hours ago
    Evan,
    Let me re-phrase, we have a total of 24 teams. These teams are broken down by Regional Managers that will have anywhere from 8-12 sub-teams (District Managers), each of these sub-teams can have 15-20 associates listed. That sub level is what I would be working with..
    So what I would want to do is this; if a Regional Manager wanted to move Larry Manz, who works under Keith Wheelden from Team 06 to Team 07. It would change the team assignment from 06 to 07 AND the Category Manger from Keith Wheelden to Kelvin Umana...
    Does this make sense?


    ------------------------------
    Hans Hamm
    ------------------------------