But as you click on it, the "+X" changes to the cascade button.

This is confusing and misleading UX.

Alina from product here. As summer arrives, I wanted to check in and ask you on your current experience with account governance, reflecting on the last year and newly releases this year. To recap what became available:

• New bird-eye admin experience across workflows, custom fields, forms, spaces and custom item types. Custom fields — recent addition
• Configuration deactivation and easy clutter cleanup
• Multi-space configurations for scalability and reusability of workflows and custom fields as recent addition (custom item types upcoming!)
• Workflow governance updates for data maintenance with required fields on status transition (recent addition!)

Questions:

1. Reflecting on the year, do you see your processes and Wrike setups improving? If so, how?
2. What are you looking forward to get improved in admin and governance experience next?

As always, appreciate your responses!

Hi Community! 👋

We’re thrilled to announce a highly requested configuration update: Multi-Space Custom Field Configuration is now live! 🚀

What is Multi-Space Custom Field Configuration?

Previously, if you wanted to use the exact same custom field in multiple spaces, you had two choices: duplicate the field or promote it to an account-level field.

In the AI era, your insights and automations are only as good as the data powering them. Now, you can create a custom field once and seamlessly share it across specific spaces. It’s the perfect way to keep your workspace clean, your field names consistent, and your cross-space reporting completely accurate! 💯

What You Can Do 👇

• Scale Faster (Reuse, Don't Duplicate): Add existing space-level or account-level custom fields to other spaces seamlessly.
  
  
• Better Visibility: Two new columns Belongs To and Added To (complete with grouping) have been added to your custom field management views so you always know where a field originated and where it's being used.
  
  
• Data Integrity : Team members will see relevant custom fields highlighted in their pickers, making it much easier to find the right fields for their specific space. Highlighted custom fields act as 'guardrails,' ensuring clean data entry while eliminating the fatigue of scrolling massive lists.

How to Manage Fields Across Spaces

🔐 How to Enable Permissions (For Account Admins)

Before diving in, Account Admins can control who can share fields across spaces:

1. Go to Settings and select User types.
2. Click Custom Fields and enable the new multi-space permissions for any role.

📂 At the Space Level (For Space Admins)

If you manage multiple spaces, you can pull fields directly from your Space Settings:

1. Navigate to your space and open Space settings (the gear icon).
2. Go to the Custom fields tab and click + Custom field.
3. Select an existing custom field from another space you manage.

Alternatively, you can "push" a field from its original space out to other target spaces:

1. Open the Custom fields tab in the field's home space.
2. Click the three-dot menu next to the field name and select Edit management and access.
3. Go to the Add to spaces tab to choose your target spaces, and use the Sharing settings tab to manage who can view/edit it.

⚙️ At the Account Level (For Account Admins)

Account Admins can manage everything centrally without diving into individual spaces:

1. Go to Settings and select Custom fields.
2. View the complete field list featuring the new Belongs to and Added to columns.

📝 Good to Know & Limitations

• Detaching vs. Deleting: Removing a field from a recipient space simply detaches it, and it won't delete the field or wipe out existing data values on your items. Fields can only be deleted or deactivated from the space they originally belong to.
  
  
• Locked & Archived Spaces: You cannot share a field out of a locked space, and you cannot add fields into an archived space.
  
  
• Formula & Database Fields: If you reuse a Formula field, make sure to add any dependent fields to the target space too. For Link to Database fields, ensure users in the new space have access to the underlying database.

✅ Availability

Available for Pinnacle and Apex plans.

Want to dive deeper? Check out our full Help Center Article for more details.

We’d love to hear your thoughts! Drop your questions, comments or use cases below! 👇

Alina from Product team here 👋 Today I am excited to bring you our newest governance addition (and a long-awaited release): Required fields on status transition!

You definitely (!) need to try it out if:

• You have a reporting process where people need to consistently provide data
• Your data tends to be outdated because people either forget to update the system or update it incorrectly
• You spend your own time doing it manually and looking for ways to delegate or optimize

Required fields unlock 2 things at once:

• Setting guardrails on status transition to ensure that your team provides the right data before proceeding
• Educating your team on work hand-off rules directly in Wrike, without spending time on additional documentation

How it works:

• Go to space or account workflows admin panel > Find a custom workflow > Select a status
• ➡️ Click 'Required fields on status selection'
• Select a field you want to require when a person tries to change this status to the next
• Next, narrow down to exact required formats like “should be X”, “should be in-between” to ensure there is no data corruption
• Save
• Now, each time a person tries to change this status to the next (and if the correct field values are missing), a mini-form will be shown requiring to complete the data

What to configure:

Although it depends on your process, popular examples might include:

• 💬 When put 'On hold' > 'Status update' / 'comment field' should not be empty
• 💰 When changed to 'In assessment' > 'Budget' field, should be no more than
• 💳 When changed to 'In assessment' > 'Client' field should not be empty
• 👤 When changed to 'In progress' > Assignee field should not be empty
• 🔢 When changed to 'In progress' > 'Story points' field should not be empty
• And so on

For more details, go to the dedicated Help Center article.

As always, let me know your thoughts in the comments below! 👇

Alina from Product team here 👋 Just recently I have announced that we've introduced required fields on status transition! Hopefully you have been enjoying the feature so far!

I am popping in to update you on the recent additions to the functionality:

• More fields introduced:
  • Due date
  • Start date
  • Duration
  • Effort
  • Name
  • Importance
  • Custom field duration
  • Custom field link to Datahub
• Admin experience improved:
  • Required fields column is now added to Workflow admin lists. It shows you which fields are connected to a given workflow. You can easily group by this column and see which workflows are affected. For example: you deactivated a custom field — in which workflows was it used?
  • Statuses column is now added to Workflow admin lists. You might not thought about it but once you see it you know you needed it: get a full overview of work stages without the need to open each individual workflow. Group to see the duplicates!

More to come!

Once a request is approved, the team is required to select the request prioritization, so in the workflow I added the requirement that the prioritization field be filled in when using this Prioritization status.

When manually changing to this Prioritization status, the pop up to select the value for the custom field works just as it should - I get a pop up box to make the selection. However when I tested the flow using the approval response changing the status field to Prioritization, nothing happens. The project status does not change at all now.

My question is, why wouldn't the approval response still trigger the status change, and have the same pop up box to fill in the custom field as it does when manually changing to the field? Why does the system just ignore everything?

I'm running into an issue with the "Get Tasks By ID" endpoint. When I request a task via the "Get Task (folders)" endpoint, I can request and see the customField values for a task. When I take the ID of one of the tasks I got back from the "Get Task (folders)" endpoint and submit it to the "Get Tasks By ID" endpoint, I get back an empty CustomFields list.

Not sure exactly what's going on here, but something is clearly not working as expected.

Alina from product team here 👋 Today I am bringing you an update related to one of the most vital configurations — custom fields!

Last year, you saw us gradually improving your admin experience for Forms, Workflows, Custom item types and Spaces with bird-eye view configuration experience and configuration usage analytics.

Finally, custom fields are here to have the same upgrade! Do not miss:

• Fresh and modern tabular experience
• Slicing and dicing methods like grouping and filtering
• Search
• Export to Excel
• Creation from the admin list directly
• And, to remind on the last year's update — real-time usage calculations that account for all activity, both manual and automatic (automation, AI, API).

I'd love to share some feedback on collecting contact information on external request forms.

It would be amazing if we could update the Contact info page questions that appear when we check off Enable public link on a request form and select Require respondent's name and email.

I know the name and email questions are mandatory, but it would be great if we could:

• Add additional questions to this page, related to contact information (ie. phone number, address, etc.)
• Be able to split up the name question (or choose if we want to ask for full name in one question, or first name and/or last name in separate questions)

This piece of feedback sprung from a specific use case. We are trying to connect requester names to our CRM via an integration through mapping the questions to separate custom fields (first name and last name fields), but we cannot add another question to this page or split the name question. We can rename the Your name question to first name and later add last name in the field OR re-add first and last name questions later in the form, but we want to avoid a choppy experience and we don't want users to have to fill in the same questions twice, respectively.

Totally understand that the email question should be mandatory if we are requiring the respondent's name and email, as we want to ensure they get emailed a copy of their submission and so that we can email requesters directly from any give work item - not trying to change this aspect of the existing feature. We just want more control over how we capture name and other relevant contact information.

Thanks!

What I’m asking for

When a value is entered/updated in a custom field in one place (ex: Project Info), that same value should automatically populate anywhere that same custom field appears elsewhere in the project (ex: tasks/subtasks used later in the workflow).

Why it’s needed

Today, teams often have to re-enter the same information multiple times (or copy/paste), which creates risk that reviewers/workers see a blank or outdated value. A linked field would:

• reduce duplicate data entry
• prevent inconsistencies
• improve handoffs during review/approval phases
• make templates/workflows more reliable

Example use case

In a project I’m working on, we have a project-level custom field called “Sponsor Link” on the Project Info page. Later during peer review, the reviewer needs that same sponsor link available on the review task(s).

I’d like the Sponsor Link field to already be populated on those tasks automatically (and stay updated if the link changes).

Ideal behavior (optional)

• Admin option when configuring the custom field like “Link to Project/Parent value” (or “Inherit from Project/Parent”)
• Option for child locations to be read-only/inherited or allow override with a clear indicator
• Updates propagate automatically to all linked instances

How it works

• Draft or archival, why not both? Use status field to turn a custom field / custom item type on or off. Use 'off' state to archive or to mark this configuration as draft.
• Admins will continue to see and be able to manage this custom field / custom item type in their admin lists.
• Data is not lost. This feature is NOT deleteion.
  • Custom item types. If a real item has already been created from a custom item type, it stays. A deactivated custom item type cannot be discovered in menus to create from it again. Item itself stays editable. A visual note will help to understand who has deactivated it and when.
  • Custom fields. If a custom field is already selected on an item, it stays on it. A deactivated custom field turns read only and menus do not allow to discover it by default (however you can enable a setting in the custom field search to discover them). A visual note will help to understand who has deactivated it and when.
• Changed your mind? It's OK. Reactivate anytime to restore the configuration and it will bounce back in places of use.
• Where to start? Helpful usage stats are already there to help make an educated decision.

P. S. With this release, you now have the full collection of tools to quickly cleanup your workspace! Other features:
- Deactivate Forms
- Deactivate Workflows
- Archive Spaces

How many unused configurations have you already deactivated? 🫧

Can you please make some additional task metrics available, particularly in gantt view, such as total slack (for each task), latest start (before becoming critical path), and latest finish?

For detailed project managers, these metrics really help to identify where effort should be placed to keep the whole thing on track. Right now we can visually estimate the slack (the horizontal space between bars on the gantt), but it is not a great way to prioritize. Data driven management is way better.

Thanks!

If you’ve ever thought, “I wish I could report on budget, channel, region, or priority directly in Wrike,” this one’s for you.

We’re excited to announce our next Wrike Essentials webinar focused on Custom Fields - the building blocks that turn Wrike into your system of record.

In this live session, we’ll show you how to capture the information your team cares about most and turn it into clear, reliable insights - without adding extra work for your users.

👉 What: Wrike Essentials: Custom Fields – Track the Data That Matters to You
📅 When: Thursday, February 26
⏰ Time: 10:00 a.m. PST
🔗 REGISTER NOW

During this live session, we’ll cover how to:

• Use Custom Fields to categorize your projects, keep track of financials, and more
• Choose the right field types for the data that needs to be tracked
• Map Custom Fields into Request Forms to simplify data collection and speed up reporting
• Turn collected data into meaningful reports, dashboards, and decisions
  

This webinar is for you if:

• You’re still storing important details in descriptions, comments, or spreadsheets 🔎
• You want better reporting but don’t have a clear structure for your data yet 📊
• You’re a space or account admin looking to standardize how your org tracks key info 🧩
• You’re a power user who wants Wrike to reflect your real processes and terminology 🧠

We’ll wrap up with a live Q&A, so bring your questions and real scenarios - whether you’re just getting started with Custom Fields or ready to refine what you already have.

We’ll also host dedicated Live Expert Office Hours on Custom Fields and Custom Item Types, where you can ask your specific questions and receive real-time guidance.

We’re looking forward to seeing you there and helping you make Custom Fields work for you!

Save your spot today or view full calendar of Wrike Essentials series