Skip to main content
Question

Project Management

  • October 17, 2023
  • 0 replies
  • 75 views
Forum|alt.badge.img+5

Hi, I am starting my new application for project management.

My application is needed to follow the different stages of the project and to assign the job/project to each worker depending on the stage.

I have different work areas with different stages of the job for each one. Actually, they use the KanBan view in other application to do this.

How do you recomend me to do this? It is possible to make only one field of stage that contains all the stages of all of the areas or how you would recomend me to do this? I need help for best practices!

Thanks!



------------------------------
Francisco Ojeda
------------------------------
    This topic has been closed for replies.

    MarceloBenavide
    Forum|alt.badge.img+8

    Hello Francisco. My comments will based on   24 years experienced how software developer. 

    The big risk with low code tools is when missing a good analysis and data design. 

    Some times the user begin to create tables with redundant data, missing relationship data, etc ..

    The most important is that you have a good analysis and MER diagram before starting to create your app.

    I will happy help you.

    PD. Do you speak Spanish?



    ------------------------------
    Marcelo Benavides
    ------------------------------
    Forum|alt.badge.img+12
    • BrianSeymour
    • Registered
    • October 18, 2023

    Hola Francisco,

    There are various ways to design and implement this based on your business goals. Here are a few ideas:

    Simple Formula
    You could create a "Formula User" field and determine this "flat" on the parent record, something like:

    If (
    [Phase] = "Your Phase", 
    ToUser("someone@example.com"),

    [Phase] = "Your Other Phase", 
    ToUser("someone.else@example.com"),

    // Insert additional Phase logic here …

    // Default
    null
)

    Child Records
    Better architecture may be to create child records representing each Project Phase and store the Assignee as a User (not Formula User) there. For example, one Project may have many Permits … and each Permit may have an Assignee (or Project Manager).

    Delegation Chain
    Another approach would be to create a "People" table where you would enter your Project Managers and (optionally) associate them to a Quickbase User (via a User field). Then, create a many-to-many relationship between People and Projects. So three tables:

    • Projects
    • PeopleProject
    • People

    Then, instead of a User dropdown field, you'd create records in the PeopleProject pivot table to maintain history of who was assigned and when.

    Typically, some combination of these three models have worked in my experience. Especially, if you add the ability to "override" an Assignee in the User Formula.

    As Marcelo advised, having a solid diagram of your business workflow is invaluable!



    ------------------------------
    Brian Seymour
    ------------------------------
    Terms & ConditionsAccessibility statement