Hi,
We are looking to implement a project portfolio and management system at our institution and I’m evaluating if Monday can meet our needs.
I have a small issue that might just be down to me having the wrong approach to the platform but I’ve searched all over but I can’t find an answer weather or not this is possible.
The scenario is this:
I have a board (Board A) that receives an item from a form. After a new item is received in Board A, I would like to trigger an automation from a status-column update on that item, to create a new board from a template, name the new board to the item name and also add this item to the newly created board.
The problem I run into is that since the new board gets its name from the item, it is not available to choose that board in any recipes as it is not created at the time of setting up the recipe.
I would like to have a recipe that performs the following process:
When status ‘Blaha’ is updated to ‘Something’, create a new board from template and name the new board to ‘item name’ and then add item to newly created board.
I have understood that this would probably be possible using Integromat, which sadly isn’t an option for us due to GDPR so it would have to be done without any third parties and webhooks.
Is this possible to do using the built in recipes or are our needs too dynamic for the Monday.com platform?
I’m keen to know the answer to this. I also wish to do this, but have the same problem - I can’t create an item in a board that does not yet exist. I also want to copy information from the existing item across to the new item at the same time. I hope someone answers you.
Unfortunately I don’t think this will work for me. I am creating a board from a template when a status changes. The template has many items in it already. That works normally in Monday. Then when the next status changes, I want it to create an item in that board and copy across some of the information. I don’t think that duplicates and uniques can use Monday.com templates.
This is something that I am looking to do as well, but perhaps a little differently.
Some projects come through that aren’t going to be approved immediately, so we have a request form. There isn’t any sense in creating the entire project structure if it is going to be rejected or put on hold.
It would be create if I could create a trigger that would copy all the information submitted into a pre-created shell that has typical steps that are needed for every project. We already have a project template that creates a board with all the items, and for those simpler ones, we can delete the un-needed items. The board could even be created into a default workspace and then moved later, but having the information submitted to an item in our request, in multiple fields, copied to a template, with multiple groups for the different phases of the project, would be a huge time-saver.
