Need to create a timeline view of participants and projects that they are working on

1

Hi! Currently, I am seeing that there can only be a timeline and where the label and Y-axis have to be the same. Is it possible to create a timeline view where Y-Axis are a set of people, X-axis are the dates, and what goes into the meat and potatoes of the timeline are different projects that they are assigned to?

Just creating a basic timeline doesn’t allow me to separate the values of the the Y-axis and the body.

2

Sounds like you’re looking for a resource capacity planning view. Is this close?

image
image1020×388 38.9 KB

If so then:

  1. Set the “Label Display” to the Project Name
  2. Group the timeline view by the Coda Person column you’re using

You may run into some hurdles depending on how you assign people to projects. For example if you assign multiple people to a project, coda will look at the combination of people as a unique value in the Y-axis instead of putting that project under the individual persons row. I believe I know a hack to solve that problem. So if you run into that share a Coda doc with the table structures and I or others can give a whirl at solving it.

1 Like
3

This is exactly right @Ryan_Hubbard1 , thank you! Here’s the link to the timeline! Look forward to hearing from you :slight_smile:

EDIT: I think I got it, thanks so much! I appreciate you stating the steps for me :slight_smile:

4

@mattics if you’d like to keep the exact same data structure then it will require a hack or data model change to get around the issue of Coda looking at each combination of project/resources as a unique value. Basically you need a table that’s flattened the project / resource assignments to 1 to 1.

I created 3 different implementation options for you here.

  1. Manually Flatten - Requires you to hit a button to get the view you’d like anytime the the resourcing has been updated (but you could put an automation to hit that button for you, but there’s a slight delay in automations)

  2. Auto Flatten - Uses ListCombine magic to populate the flatten data, but has a limitation. Maybe a better option to use #1 with an automation.

  3. Assignments table - Change your data model to 3 tables: Projects, Resource and Assignments. Assignments table rows assign 1 resource to 1 project. So if Resource A is assigned to 3 projects there’s 3 separate rows. This is the simplest implementation and not a bad option.

1 Like
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.