Do you use custom fields? We’d love to hear from you!
Прикреплено Выделено Завершено
Hi, everyone!
If you've ever spent too much time managing custom fields, wondering which fields to use, or had to create new ones to stay organized, we'd love to talk to you.
Why are we doing this?
Custom fields are at the core of how many teams organize work in Wrike. But as your workspace grows, managing and finding the right field can become a challenge. That’s why our team is researching ways to make custom fields more intuitive and easier to use — whether you’re creating tasks, setting up automations, working with forms or tables, or creating new item types.
Who are we looking for?
We want to hear from people who use custom fields often and have thoughts, challenges, workarounds, or ideas for improvement. Whether you’re an admin, a project manager, or someone who loves a well-labeled column, your input can help shape future updates.
Interested?
Leave a comment, and we’ll reach out to schedule a quick 30-40 minute call. Your feedback will help guide our next steps.
Thanks in advance for helping us make Wrike better for everyone! 💚
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
Kendra Ciszczon and I are always interested in giving feedback on custom field management! Sign us up for a joint session!
Our enterprise uses various custom fields in our account. Would be happy to give you some feedback, as management and compliance of our custom fields is always top of mind for us.
I'm interested!
Custom fields are a key part of my design process when creating Wrike spaces for my organization. Would love to participate.
I love custom fields and would be happy to discuss/share suggestions
My team relies heavily on custom fields, and we need to be able to leverage them across multiple spaces. Our only real workarounds right now are to use blueprints and dashboards as much as possible, but we really need a way to manage/administer them across multiple spaces without making them account level. We also have a lot of challenges between project vs task level fields - we need better ways to tie the data in task-level fields to the parent projects and vice versa, as well as build automations that can act on multiple levels. (For example, if the value of a given CF on the project is X, act upon a custom field in the child task to populate it with the same value.) It would also be a huge improvement if recurring tasks can be set to copy CF field values into new repeating instances.
I'll be a part of this! The biggest things I've been thinking about with custom fields are:
I have created and use a fair number of custom fields and would be open to discussing.
Thank you.
Please include me. Custom fields are critical to all the work my team does and being able to organize and track our work in Wrike. I need to be able to copy custom fields from one Space to another, including locked spaces. I spend a lot of time recreating the definition and values of custom fields in one project when I then Use that project as a templet/starting point for the next project. I can't use Blueprints as these are with locked spaces.
Custom fields are a vital part of my business process. Please count me in.
Hi Lisa, I'd love to participate in this. We have 240 Custom Fields and there are some improvements I'd like to brainstorm with Wrike to help reduce the number of fields, stay more organized, and make for easier column header views in Dashboards and Tables.
Hi Lisa,
I'd be very interested in chatting and sharing my custom field thoughts!
Interested!
I'd love to participate!
Hi!
We use a lot of them, for sure what I would like to have is:
1- A well organized table where I see all my custom fields, with the possibility (for each one) to insert a description of why they were created
2- The possibility of having custom fields only for tasks and not necessarily (project, folders, task).
We've been using Wrike for 9 years and have a large scope of custom fields and use cases. We'd be happy to discuss with the Product Manager since we definitely have some improvement ideas!
-
Inherit custom field values from parent to child items, which is probably the most requested missing feature since 2017 and been on Status: Backburner for years. See for example Custom fields of a folder and being important should be attributed to tasks/issues in that folder (149 upvotes) and Cascade Custom Field "Value" from Folders/Projects to Sub Projects/Folders/Tasks (277 upvotes).
-
"Conditional approvers" in custom workflows based on people-type custom fields We use people-type custom fields to indicate responsible persons in our projects, and they are very useful for filtering and grouping in New Table Views. What we lack are approvals in custom workflows. Yes, the approvals in custom workflows functionality exists, but we can't use it. It assumes we can set specific named users (or the project owner) as the approver in each custom workflow step. That would apply to every single project or task using that custom workflow. But that's not possible in our company, where approvers vary depending on what department or business area the project or task belongs to. We could theoretically create variations of all custom workflows for every possible combination approvers, but managing that would be a nightmare, and it would also lead to variations of all blueprints including those custom workflows, and that would be a double nightmare. "Conditional approvers" in custom workflows would be a better solution. We already have the responsible user selected in a people-type custom field. With "conditional approvers" we could select a people-type custom field as the approver in the workflow step (e.g. "Business Director", "Concept Lead", "Production Manager", "Layout Designer", etc) and the approval would be assigned to the user selected in the custom field.
+1 to Amy Augustyniak's, Delaney Murtaugh's and Pietro Poli's comments!Very interested in participating (time permitting - would be possible within the next 4 weeks).
Hello, we are interested in giving the feedback. Thank you.
Thanks Devree Czupinski! I know one thing that would be extremely helpful for us is to be able to see all of the locations the custom field is being used. We have some duplicative custom fields, but are struggling to get them "cleaned up" due to not knowing exactly where each of the fields is actually being used.
Custom Fields stands out as a pivotal feature of Wrike, enabling personalized data collection and customization tailored to specific projects or tasks. Currently, locating and sharing custom fields across spaces presents an opportunity for enhancement.
Potential feedback:
-Personally, when managing settings in a table view, the columns offered cannot be customized. This lack of flexibility hinders the builder's ability to create a tailored view for efficient management. For instance, columns such as Author, Belongs to, and Apply to may lose their value when a single individual is managing the space.
-Identifying a custom field can be challenging due to the prevalence of naming conventions across different groups. I frequently find myself editing my custom field by adding a symbol to differentiate it from other custom fields with the same name.
-Account level custom field lack flexibility as the only way to edit these requires a ticket to support. This creates a delay for users.
I'd be happy to join this also.
Very interested! 🙋♀️
Custom Fields are the primary way we pull a lot of our reporting yet one of our biggest challenges is making sure all the fields get filled out properly. And with 200 users and only 4 PMs it becomes very difficult to manage the data being entered properly. Would love to hear from others how they make sure all the information they need gets filled out properly when your a small yet mighty team.
Hi!
I would also love to be part of this!
FYI related to automation based on custom fields:
Automation Rules: Notify/Mention users from custom field type "user" (created by Marco Eberl, May 23, 2023)
Customfields in Automation. (created by Florian Gascho, June 26, 2024)
The custom field permissions in Settings (account or space field, who can see and edit field values in spaces, items, and views) are excellent.
However, as an admin with wider than regular access, I often find that when sharing my Wrike screen with other users, there are questions about restricted custom fields not typically visible (or usable) to everyone.
Would it be possible to visually indicate in the UI which custom fields have restrictions?
Also, with a large number of custom fields, it's impossible to remember which of them have restrictions. A visual indication would be helpful, for example, in order to avoid adding restricted fields to a Table View that is intended for everyone.
Jessica Bargenquast We recently had trouble with certain custom fields not being filled, and got this advice from our CSM:
Created a dashboard based on this, and have managed the empty fields using it!
It would also be great to have an automation trigger for "Custom field has been empty for [amount of time]". Then you could add the appropriate action, for example notify the owner.
Please sign me up. One top-of-mind improvement would be greater clarity and flexibility in who can edit the values of a picklist custom field vs. who can access the field to choose an existing value. (It seems we've had to grant edit rights for most users to be able to consume the field - but I could be missing something.) Lots of great feedback above!
I'd love to discuss Custom Fields from the Account Owner perspective! 🙋♀️ Our wish list of enhancements includes:
Outside of enhancements, we just need an easier way to identify where they're In Use (Folders/Projects, CIT's, Blueprints, Dashboard Pivot Tables - they could be coming from a variety of source locations) as we're troubleshooting why so many random custom fields are showing up on items.
Thanks!
Yes please!