Hello,
I’m still working on my multi-board concept, before I can put it into production:

I’d like to find a way to create a standard structure (template) based on certain criteria.
In principle, when I launch a new program, I would need several projects that are overall identical to previous projects. That is, projects composed of the same phase structure, and these phases depending on the same list of deliverables.
Currently, if I duplicate rows from a board, the elements “connected” by relation from upstream and downstream boards are not duplicated.
I am linked to the same elements and must manually create the other duplications and then recreate all the links.
Would it be possible to imagine a “Creation Form” where I could navigate through the relationships to create my structure?
As a reminder, here are the links:

Thank you,
Have a good day,
Antoine
1 Like
Hello Antoine. The concept of a template (model) for an entire linked structure is very interesting. This has been brought up to us multiple times.
Especially in the context of a portal that we would like to reproduce N times, and which would point to a structure of several boards, linked or not.
We are thinking about creating all of this, as it is essential for consulting firms that need to repeat missions starting from a structure.
For now, duplicating a board with relationships is possible. It’s an option to check in the duplication screen (from the homepage where you see all the boards).
1 Like
Hi,
I’m not necessarily looking to duplicate an entire set of boards, but rather to duplicate an entire “Project” item with its set of “Phase” items and all the “Deliverable” items associated with the “Phase” item.
That way, when I want to start a new Program item, I can select several “Project” template items that I duplicate, and it already gives me all the associated “Phases” and “Deliverables”.
My boards always remain the same because all views are well configured.
Is that clearer?
Have a good day,
Hello Antoine,
You want to do a kind of “deep-copy”. Do you want to do it while staying within the same boards, or do you want to recreate a new board hierarchy with your data subset?
Hi @Gaël_PAQUET,
What I would like is to be able to stay in the same Board to enrich it with new elements.
The goal is to have a good structure, and then to be able to enrich it with elements gradually.
Scenario:
- I establish the correct board structure
- Boards: Program - Project - Deliverable Phases
- I establish the specific attributes for each board
- I set up board-to-board dependencies
- I add internal dependencies to the Board (Phases can depend on another Phase, Deliverable can depend on another Deliverable)
- I make attributes roll up: Lookup
Example:
- Deliverable progress → rolls up to Phase → rolls up to Project → rolls up to Program
- Start and end dates of phases → rolls up to Project → rolls up to Program
- Program name → cascades down to Project → cascades down to Phases → cascades down to Deliverable
- Project Manager → cascades down to Phases → cascades down to Deliverable
- Construction of all views for manipulation
Example:
- Gantt chart view with Phases and their dependencies grouped by Project grouped by Program
- Kanban Deliverable “user” view: To do / In Work / Done
- …
- Creation of a Portal for accessibility and rights management
- Construction of the structure
- establishment of groups
- …
- Creation of element templates
- Project type → broken down into phases → composed of deliverables
- Creation of multiple element types
- Launch of the first Program
- Selection of project templates to meet this program
- By copying, the projects of this new Program come with their corresponding Phases and deliverables
- adjustment of attributes
- name of elements
- Start / end date
- responsible person
- etc…
- Launch of other Programs
- Always within the same board structure
- same as for the first program, selection of project templates / adjustment of attributes / …
=> Board indicators take into account all Active Programs.
=> Multi-level granularity management
Hi Antoine,
Yes, I think I understand your need. You want to create some templates for hierarchical elements. The difficulty is doing it generically, which means we need to imagine the right ergonomics.
To be a bit clever, we could use relationship typing. When we create master/detail relationships (which I hope you’ve done in your use case), we can consider the descendants to be an integral part of the parent to be copied (we treat it this way during deletion).
One idea could therefore be that when we ask to duplicate an element, we also offer to duplicate its descendants, limiting ourselves to master/detail relationships. Are you following me?
1 Like