<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>blueprints — Wrike Community</title>
        <link>https://community.wrike.com/</link>
        <pubDate>Sat, 04 Apr 2026 00:29:09 +0000</pubDate>
        <language>en</language>
            <description>blueprints — Wrike Community</description>
    <atom:link href="https://community.wrike.com/discussions/tagged/blueprints/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Start Project from Blueprint with New Gantt Chart by default</title>
        <link>https://community.wrike.com/discussion/2857/start-project-from-blueprint-with-new-gantt-chart-by-default</link>
        <pubDate>Tue, 31 Mar 2026 12:53:56 +0000</pubDate>
        <category>Product Feedback</category>
        <dc:creator>Ilya Linkov</dc:creator>
        <guid isPermaLink="false">2857@/discussions</guid>
        <description><![CDATA[<p>Hi Wrike,</p><p>We have plently of projects that are created from the standard blueprint. The blueprint is set with "New Gantt Chart" view, however the users must always activate manually "New Gantt Chart" view when they're creating the project X from the Request Form (blueprint).</p><p>Can we enable by default the "New Gantt Chart" view automatically for the blueprints / all users to avoid this?</p><p>New Gantt Chart view is very powerful, we don't see any usage now for the old Ganttchart view.</p><p>Many thanks.</p>]]>
        </description>
    </item>
    <item>
        <title>💡Wrike Enhancement Request: Validation Controls, Mandatory Time Logging &amp; Blueprint Defaults</title>
        <link>https://community.wrike.com/discussion/2852/wrike-enhancement-request-validation-controls-mandatory-time-logging-blueprint-defaults</link>
        <pubDate>Mon, 30 Mar 2026 13:35:54 +0000</pubDate>
        <category>Product Feedback</category>
        <dc:creator>Sambit Kumar Behura</dc:creator>
        <guid isPermaLink="false">2852@/discussions</guid>
        <description><![CDATA[<p>🚀 <strong>Business Requirement</strong></p><p>We are looking for enhanced validation capabilities within Wrike to improve data governance, consistency, and reporting accuracy across projects and time tracking.</p><ol><li>🛑 <strong>Project &amp; Location Validation (Soft &amp; Hard Validation):</strong><ul><li>Introduce configurable <strong>soft and hard validation rules</strong> when users:<ul><li>Delete a project</li><li>Change a project’s location</li><li>Remove a project from its original location</li></ul></li><li>⚠️ Soft validation: Warning prompt (e.g., “This project is part of a governed structure. Are you sure?”)</li><li>🔒 Hard validation: Restrict action unless specific conditions or permissions are met</li></ul></li><li>⏱️ <strong>Mandatory Time Logging Fields:</strong><ul><li>Enable the ability to make <strong>time logging category a required field</strong> when users log time</li><li>Prevent submission of timesheets unless all required fields (e.g., billable vs non-billable category) are populated</li><li>⚙️ Allow admins to configure required fields for time entries at the account or space level</li></ul></li><li>🧩 <strong>Blueprint-Level Default Time Logging Categories:</strong><ul><li>While creating blueprints, we already define task structure and ownership; similarly, we should be able to:<ul><li>Define whether each task is <strong>billable or non-billable</strong></li><li>Assign a <strong>default time logging category at the task level within the blueprint</strong></li></ul></li><li>🔄 When the blueprint is applied to a project, these defaults should automatically carry over to tasks</li><li>💡 This would significantly streamline time tracking and reduce manual effort for users</li></ul></li></ol><p>📉 <strong>Impact</strong></p><p>The absence of these capabilities is creating significant operational and reporting challenges:</p><ul><li>🧱 <strong>Data Integrity Issues:</strong> Users can unintentionally remove projects from governed spaces or delete them without safeguards, leading to loss of structure and visibility</li><li>📊 <strong>Reporting Inaccuracy:</strong> When time logging categories are not enforced:<ul><li>Leaders cannot accurately distinguish between <strong>billable and non-billable work</strong></li><li>Utilization metrics become unreliable</li><li>Financial and capacity planning reports are compromised</li></ul></li><li>😓 <strong>Inefficient User Experience:</strong><ul><li>Users must manually select time logging categories for every entry</li><li>This increases the likelihood of errors or skipped fields</li><li>There is no standardization even though work is already standardized via blueprints</li></ul></li><li>⚡ <strong>Missed Automation Opportunities:</strong><ul><li>Time tracking is a critical component tied to deliverables and reporting</li><li>Without default values at the blueprint level, we lose the ability to fully automate and standardize execution</li></ul></li><li>🧭 <strong>Governance Breakdown:</strong><ul><li>Projects can be moved or altered outside intended structures</li><li>Teams may bypass workspace hierarchy, impacting reporting and visibility</li></ul></li></ul><p>✅ <strong>Conclusion</strong></p><p>Introducing validation controls and blueprint-level defaults would significantly strengthen Wrike’s governance, usability, and reporting capabilities.</p><p>These enhancements would:</p><ul><li>📌 Ensure <strong>consistent data entry and enforce governance standards</strong></li><li>📈 Improve <strong>accuracy of utilization, billing, and operational reporting</strong></li><li>⏳ Reduce <strong>manual effort and user errors in time tracking</strong></li><li>🎯 Create a more <strong>intuitive and optimized user journey</strong> by aligning execution with predefined blueprint structures</li><li>🤖 Support Wrike’s vision of intelligent, standardized workflows where processes are automated and scalable</li></ul><p>Overall, these features would enable organizations to operate more efficiently, maintain control over their workspace, and fully leverage Wrike as a reliable system of record.</p><p>Please, let us know if any other additional information is needed, we would be more than happy to work with you.<br /><br />
Cheers,<br />
Sambit</p>]]>
        </description>
    </item>
    <item>
        <title>Start constraint information in Activity Stream</title>
        <link>https://community.wrike.com/discussion/2816/start-constraint-information-in-activity-stream</link>
        <pubDate>Mon, 16 Mar 2026 17:57:46 +0000</pubDate>
        <category>Product Feedback</category>
        <dc:creator>Anna Giacobbe</dc:creator>
        <guid isPermaLink="false">2816@/discussions</guid>
        <description><![CDATA[<p>Hi team! </p><p>A small piece of feedback regarding<strong> start constraints:</strong> it would be extremely helpful to get information on the addition/removal of these at the task-level in the Activity Stream. </p><p>Right now, this type of change doesn't record and I know a lot of these get added accidentally, so having an audit trail of when these get added (or removed) would help admins with their investigations to see if it was intentional or accidental. This applies to blueprints and real/active work.</p><p>Thanks! </p>]]>
        </description>
    </item>
    <item>
        <title>Creative Ways to Launch Project from Blueprint for Wrike Newbies</title>
        <link>https://community.wrike.com/discussion/2695/creative-ways-to-launch-project-from-blueprint-for-wrike-newbies</link>
        <pubDate>Sun, 15 Feb 2026 23:59:47 +0000</pubDate>
        <category>Solutions Corner</category>
        <dc:creator>Rob Gorczyca</dc:creator>
        <guid isPermaLink="false">2695@/discussions</guid>
        <description><![CDATA[<p>I have a new employee who will have the need to create new projects on a regular basis. I'm going to create a blueprint, since the project will be the same every time. I'd rather avoid the "create a project from a blueprint" option. I'm a very experienced user and even I find that to be tricky (hunt for the blueprint, then have to make sure the right fields are selected or unselected).  </p><p>I'm leaning toward creating a short submission form, which is how I spin up most new projects from blueprints. This also will allow me to place the folder in the new employees space/folder.  </p><p>Am I missing anything that could be even easier than using a submission form?  Any automation process that I'm overlooking?   </p><p>I may just be over thinking this, but it seems like there should be an easier option than having to resort to a submission form.  </p><p>Thanks in advance! </p>]]>
        </description>
    </item>
    <item>
        <title>Wrike Essentials : Work Smarter Series  Live Expert Q&amp;A - Request Forms &amp; Blueprint</title>
        <link>https://community.wrike.com/discussion/2686/wrike-essentials-work-smarter-series-live-expert-q-a-request-forms-blueprint</link>
        <pubDate>Thu, 12 Feb 2026 15:38:10 +0000</pubDate>
        <category>Announcements</category>
        <dc:creator>Pradyusha Patro</dc:creator>
        <guid isPermaLink="false">2686@/discussions</guid>
        <description><![CDATA[<p>Fed up with constant manual, repetitive tasks when request forms and Blueprints could be keeping your work moving automatically in the background?</p><p><br />
Join our live webinar on February 18 at 10:00 AM PST to discover how Wrike Request Forms and Blueprints help you reduce manual work, keep tasks moving forward, and standardize processes — with no extra effort.</p><p><br />
Don’t miss your chance — Register now! (Registration Link - <span data-embedjson="{&quot;body&quot;:&quot;&quot;,&quot;url&quot;:&quot;https:\/\/community.wrike.com\/home\/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fdiscover.wrike.com%2Flearn%2Fcourses%2F2230%2Flive-expert-qa-request-forms-blueprints&quot;,&quot;embedType&quot;:&quot;link&quot;,&quot;name&quot;:&quot;Loading&quot;,&quot;embedStyle&quot;:&quot;rich_embed_inline&quot;}">
    <a href="https://community.wrike.com/home/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fdiscover.wrike.com%2Flearn%2Fcourses%2F2230%2Flive-expert-qa-request-forms-blueprints" rel="nofollow noopener ugc">
        https://discover.wrike.com/learn/courses/2230/live-expert-qa-request-forms-blueprints
    </a>
</span>
)<br /></p>]]>
        </description>
    </item>
    <item>
        <title>include items type in import and export excel</title>
        <link>https://community.wrike.com/discussion/2670/include-items-type-in-import-and-export-excel</link>
        <pubDate>Mon, 09 Feb 2026 10:13:29 +0000</pubDate>
        <category>Product Feedback</category>
        <dc:creator>Charlotte Wicht</dc:creator>
        <guid isPermaLink="false">2670@/discussions</guid>
        <description><![CDATA[<p>Hello,<br />
would be great if when exporting &amp; importing an excel wrike recognize the item type.<br /><br />
Our use case:<br />
When we are prepare a futur blueprint we have to remove the prefix on all tasks. in order to do it i have to export made a find and replace in excel than import again in Wrike to have the correct naming for the blueprint. BUT item type is not part of it so i have to re change all the items type.<br />
This possibility would improve our process. because when you have a blueprint with 200 tasks it's time consuming to remove the prefix one by one. Or improvement could be done on convert a project to blueprint by using AI recognizing a define prefix and remove it.<br /><br />
Thanks.</p>]]>
        </description>
    </item>
    <item>
        <title>Wrike Essentials: Blueprints – Run Projects With Confidence and Control</title>
        <link>https://community.wrike.com/discussion/2661/wrike-essentials-blueprints-run-projects-with-confidence-and-control</link>
        <pubDate>Thu, 05 Feb 2026 05:19:52 +0000</pubDate>
        <category>Announcements</category>
        <dc:creator>Janaki Ramakrishnaiah</dc:creator>
        <guid isPermaLink="false">2661@/discussions</guid>
        <description><![CDATA[<p>Stop wasting time setting up projects from scratch—Wrike Blueprints can help you standardize work, save time, and launch projects consistently.<br /></p><p>Are recurring projects and workflows taking too much effort? Are teams spending more time configuring tasks than actually doing the work? Let’s fix that.</p><p>Join our upcoming webinar:</p><p> <strong>Date:</strong> February 24, 2026</p><p><strong>Time:</strong> 9:00 a.m. PST</p><p><strong>Topic:</strong> Wrike Essentials: Blueprints – Run Projects With Confidence and Control</p><p>By the end of this session, you'll be able to:</p><ul><li><strong>Understand the purpose and benefits</strong> of Wrike Blueprints for standardizing work</li><li><strong>Create and configure Blueprints</strong> for recurring projects, tasks, and workflows</li><li><strong>Launch projects and tasks</strong> from Blueprints with minimal setup time</li><li><strong>Manage ownership, permissions, and organization</strong> of Blueprints across teams</li><li><strong>Apply best practices</strong> to keep Blueprints clean, scalable, and easy to maintain</li></ul><p>We’ll walk through real-life Blueprint examples, share practical setup tips, and show you how to build Blueprints your teams will actually use. There will also be time for <strong>live Q&amp;A</strong>.</p><p>Whether you manage a single team or an enterprise setup, this webinar will help you reduce repetitive setup work, keep projects consistent, and make Wrike work smarter for everyone.</p><p>Don’t miss out — <strong>[</strong><a href="https://community.wrike.com/home/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fdiscover.wrike.com%2Flearn%2Fcourses%2F2208%2Feliminate-starting-from-scratch-by-deploying-proven-project-structures" target="_blank" rel="nofollow noopener ugc"><strong>register today on Wrike Discover</strong></a><strong>]!</strong></p><p>If you’re joining us, drop a comment and let us know:<br />
 What’s the biggest challenge your team faces when setting up recurring projects in Wrike?</p>]]>
        </description>
    </item>
   </channel>
</rss>
