Creating Projects from Blueprints and Losing Task Statuses
I just recently discovered and have been experimenting with using Blueprints. My company has multiple departments that need to review and edit each project before it is ready for the rest of the company to use. It seemed like Blueprints were the perfect feature for this.
We used Blueprints as a preparation area and updated our task statuses to show which tasks were complete, make notes, etc. I am now ready to move the project to the main folder so the rest of the company can access. When I "create a new project" from the blueprint, the task statuses disappear (the tasks that were marked as "complete" are now showing as "new").
Is there a way to update the project in Blueprints and then keep the statuses the same when I use the Blueprint to create a project?
By creating projects this way, am I losing any of the other edits made to the Project when it was in Blueprints?
Hi Stephanie,
I've been using the Blueprints feature pretty extensively for the past couple of weeks and am loving it, but I don't believe that it has the flexibility to set and keep statuses when you use the Blueprint to create a new task.
In fact, I just tested the "Duplicate" action on a task with subtasks at various statuses, and that reset the statuses on each one to "New" as well. So it seems to be a common behavior throughout the platform.
However, if I'm understanding your post correctly you may not need to use the Blueprints feature at all. When you prepare a task in Blueprints, do you need to use an exact copy of that prepared task multiple times? Or are you adding notes and statuses specific to one instance of that task?
If the statuses are case-specific and different every time you prepare the task, then you may want to create a private folder in your "Personal" workspace just for preparing those tasks. That way nobody else in the company would have access to it before you're ready to share it. (see my screenshot below)
Once you're ready to share it, you can easily move the task into the shared company folder by click-and-dragging it from the List View to the appropriate folder in the Navigation bar. That way, all your statuses and notes will remain intact because it's the exact same task, just moved somewhere else.
The Blueprints feature is more useful for making exact copies of a "blank" version of task to start from scratch. For example, we use a blueprint every time we need to onboard a new employee following the exact same steps every time.
I'm having the problem, any statuses that "Canceled", "Completed", or "Deferred" are always replaced with the first status from the "Active" category. Can we have the option to keep statuses (from any category) when creating from a blueprint? Thanks
Hello Naz Khatun, welcome to the Community 👋🏻
I see that you're in touch with our Support team. As my colleagues mentioned, it's currently not possible for tasks with "On hold", "Canceled", "Completed", or "Deferred" statuses to keep the status when created from the Blueprint. I can suggest you create a project/folder template to use to duplicate as a workaround. Let me know if I can help with anything else 🙋🏻♀️
Hi @..., I did see this workaround, thank you. We have quite a few blueprints and would rather our team didn't create projects in their personal space. This way we have one blueprint for the project/tasks, can easily see the changes over time and can easily keep a blueprint updated. Hopefully this is something Wrike will look into in the future :)
I understand, thank you for the clarification and feedback Naz Khatun 😊
We NEED this functionality. I have a request form that pulls from a blueprint where the main task is active and the subtasks are "on hold". Whenever the task is created, the subtasks are marked with an active task status. We want the subtasks to be a deferred status as they might not be needed until much further along in the process.
Thank you for supporting this suggestion and sharing your use case Ashley Fischer! Our Product team is aware of this feedback; we'll let you know if there's an update on this.
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Any updates on the functionality?
Hi Christine Covington, thank you for checking in here. There are no updates in relation to this request at the moment, we'll be sure to let you know if there are any changes👍🏼
Hi everyone, a quick update from the Product team - you can now preserve statuses when creating projects from Blueprints 🎉
Hi Cansu, I found this thread when looking for a solution to our similar problem. We have a series of Blueprints that should start in an "On Hold" status, while their subtasks (also Blueprints) start in "Submitted," the top Active Status of the Workflow. This Blueprint is coming from a request form. However, we're finding that all the tasks and subtasks are showing up in "Submitted" status. The subtasks need to be completed first before the parent task can be completed, which is why it needs to be deferred.
I see here that you say you can preserve statuses when creating Projects from Blueprints. Does the same not hold true for Tasks? If that's the case, why the discrepancy? Is there any chance Task Blueprints will be able to hold statuses when created from a request form any time soon?
Thank you!
Hi Michelle,
it's strange. I've some blueprints that have "deferred status" tasks and I'm able to create them.
Are you sure that project launched shows all tasks?
Can you share some screenshots to help you better?
Hi Pietro Poli,
It's when tasks are created by a request form that their "On Hold" status defaults back to the top active status, "Submitted." Just creating the task or subtask from a Blueprint in a deferred status works fine -- it's creating one from a request form that is the key ingredient causing us problems.
We are going to try a workaround of "faking Wrike out" by creating a new status that is an active status but is named in a similar way and with the same color as our "On Hold" statuses. Then hopefully it will not see this as a deferred status and change the status on us. It's a bit of a clunky solution, but it might work...
Great Michelle!
I've made the same with a "fake deferred status in active"