Custom Fields for Tasks ONLY

Unless I'm missing something, it would be really nice to have the option to apply a custom field to ONLY THE TASK vs having to apply it to "tasks, projects, and folders". The way we set up work in Wrike is to have a project that is then populated with various related tasks (I assume that's how a lot of people use it). In a lot of cases there are things we would like to denote as custom fields that only apply at the task level and not at the project level. Having them also populate at the project level is cluttering and confusing.

Find more posts tagged with

Gathering votes

Status: Gathering votes

Comments

Amanda Juneau

I agree with this! Task level fields would be so helpful are very much needed. There are a few fields that we only want shown at the task level and have no business appearing at the project/folder level. It becomes cumbersome to look at all the custom fields at the project/folder level that are irrelevant to those containers.

Elizaveta Bogdanova

Hey folks, thank you for this feedback!

Have you tried using Work Templates yet? It's an experimental functionality that account owners and admins can enable from Wrike Labs. When you use them, you can set up which custom fields can be visible on tasks created from those work templates.

Please let me know if that can be helpful!

Anna Welsh

@Elizaveta Bogdanova I am trying out the project template functionality now and it seems to be addressing my needs around the custom fields. But it also seems to be missing the aggregation of time spent on a project (rolled up from time logged to its tasks). Is it there somewhere and I'm missing it or does it not exist in this project template view?

Cansu Yetisgin

Hello @Anna Welsh, currently, rolled-up time is not part of Work Templates, I'm sharing your feedback with our Product team 👍🏼

Regina Ball

Yes, I desperately need this! It's confusing for my team when task-specific custom fields apply to projects. I know Work Templates are a workaround, but this is an issue for all of our existing projects.

Elizaveta Bogdanova

Thanks a lot for supporting the suggestion here, @Regina Ball!

Tess Brown

We currently use Wrike as a project management system. We are so close to also being able to utilize a space in Wrike for ad placements, but there is one thing stopping that! Our need is to have Project Specific Custom Fields and then Task Specific Custom Fields. Currently, the project has triple the amount of necessary fields in order to get them accessible on the task. I tried Work Templates but it was too clunky for our needs. Please, make make custom fields have a task-only option!😍

Elizaveta Bogdanova

Thank you for detailed feedback here @Tess Brown! The Work Templates functionality should definitely help with this suggestion, and our Product team has plans to continue updating and improving it. We will be sharing all those updates here on the Community 😊

Khashayar Mirfassih

Hi Lisa, our team would love to have custom fields on task only. I am in a similar situation where the custom fields on the project level are useless as they are only used on tasks. Making the project itself look long, empty and inaccurate. It would be great if we could differentiate between tasks and projects it would also help load the project faster.

Cansu Yetisgin

Hi @Khashayar Mirfassih, thank you for chiming in here and sharing your use case. I'm passing it on to our team👍🏼

Stephanie Castilla

My need for this has more to do with data entry than viewing.

I need this when I am bulk editing a custom field in table view - using the blue dot in the corner of a cell that can be dragged to replicate content down a column. I need custom fields that only apply to tasks so I can easily drag and copy values down a column without applying the values to the container projects and folders.

This would be incredibly helpful to avoid much wasted time clicking and entering values row by row.

Elizaveta Bogdanova

Thanks a lot for sharing your use case @Stephanie Castilla!

The general ask in the original post has recently become possible with Custom Item Types - you can create a project-based item and hyde custom fields on the panel. Please let me know what you think and whether this can help!

Todd Kelvington

I don't see how Custom Item Types addresses this issue. If a Custom Item Type is at the Task level it still behaves as a Task even though it may be called something different. My only choices for applying custom fields are:

tasks, projects, and folders
projects and folders
projects

So I still cannot apply a custom field to anything at the task level without it also being at the project and folder level.

Elizaveta Bogdanova

Hey @Todd Kelvington, welcome to Wrike forums 👋 In custom item types (for example, in project types), it is possible to hide certain fields:

Could that be helpful for you?

Stephanie Kirk

Desperately need this for our new system to work. I need to have someone fill out a request form that produces a project with specific tasks from a blueprint. At the moment the only thing I can think of to do is choose a blueprint based on the answer chosen and have the task custom field already set on that blueprint. But, that means I will need over 50 blueprint tasks. Not great, and open to human error when we need to update things. Basically, if we could map custom fields from a request form answer to either a project or a task custom field that would be MAGICAL.

Juan Muttoni

Hi @Stephanie Kirk, thank you for supporting this idea and for sharing your use case with us. I've passed your comments on to our Product Team 👍

Keith Riess

Hello Wrike Team!

I agree that having custom fields only at the task level would be a great feature to have in the tool! Right now, our organization created certain custom fields at the task/folder/project level which are completed by team members in the tasks, themselves. These task custom fields are connected to an automation created by the Wrike Integrate team, where data is pulled from these tasks fields and output in a spreadsheet once a month, which our management team uses for billing purposes. However, these fields also show as blank fields at the project level, where the data input isn't required.

It would be great to hide these fields at the project level, so there aren't any unnecessary custom fields showing that just aren't being used.

Juan Muttoni

Hi @Keith Riess, thank you for sharing your feedback with us, it's with our Product Development Team now 👍

We will keep you updated in case there are any improvements implemented 🙂

Calvin Aldag

Hello,

are there any updates from the product team here? The first request is from 2021 - it would be great if we could get this feature in Wrike.

Basudha Sakshyarika

Hey @Calvin Aldag! Great to have you in our Community!

Thank you for taking the time to share your feedback. Currently there are no updates to share. We will definitely keep you in the loop anything changes.

Also, the original post is on the lower side of upvotes, so please make sure to upvote the post if you haven't already. You can find out more information on how our product feedback forum works, here. Thanks!

Leanne Downs

This request is very similar to this one: /hc/en-us/community/posts/360013767814-Custom-Field-properties-option-to-apply-to-tasks-and-subtasks-only?page=1#community_comment_28927562748695

Could they please be combined along with the upvotes?

This continues to be a need within Wrike. Typically at the Project Level, the fields/custom fields needed are at a higher level than the Tasks are and not having the ability to keep the layout clean with the best fields for the level of detail creates "noise" that tends to be ignored, whereas with the right fields on the right level (task vs project) of detail it is easier to communicate "If the field exists, it needs to be populated."

Thanks!

Rohan V

Hi @Leanne Downs 👋

Thanks for pointing out a similar feedback post. We can't combine the posts because our system doesn't allow it. However, all comments are sent to the relevant team. We will let you know if there are any updates or changes in the future regarding this suggestion. Also, thank you for sharing your feedback!

Cathy Snyder

For those trying to remove fields showing on Projects or tasks, I have figured out a work around. First you create your custom field. Then you create a custom item type for either a project or task. Add the fields that you wish to see for that item. Any fields left in the list for Add Field need to be added and then you can hide them to remove them from view. Also, if you add a custom field to be only on Space Level, the custom item type must also be on the Space Level. We found if the custom field is on a Space level, but your Custom Item type is on the Account level, you will not be able to select the field to hide it.

The issue we are having though is that the custom item type is showing up on the Folder level. Since you can't create a Custom Folder Item, I haven't figured out how to remove the unnecessary fields from the Folder. There are some things we would like to see just at the folder level since we use those as Client Containers. Having some client specific information on the Folder would be nice to keep it all contained in one place and not have to add it to all project level items.

Daisy Hibbard

I upvoted this idea a long time ago, but adding my voice to say this would be SUCH a nice feature to have, especially for account admins. We have quite a few custom fields we designed to only ever be used for tasks, not projects or folders. So the issue is that these custom fields create a ton of extra clutter on projects and folders. It makes it difficult for me to quickly find the fields I need to fill out on a project.

For example, I'm looking at our #1 priority project and out of the 28 custom fields applied, 12 of them should only be applied to tasks. 43% of what I'm looking at is just noise that slows me down.

I understand a workaround is to create custom item types, but that would add an additional layer of complexity if we applied it to all tasks, especially since pretty much everyone at my company uses Wrike in different ways. We want to use the default functionality as much as possible to keep our processes simple and easy to manage.

Thanks for the consideration!

Rohan V

Apologies for missing your comment earlier, @Cathy Snyder! Thanks a ton for sharing your workaround, your feedback is noted and has been forwarded to the team.

And thank you as well, @Daisy Hibbard. Your example is very clear and really helps our Product Team better understand this use case. If there are any updates or changes, we’ll be sure to keep you both posted 👍

Ana Hughes

Adding a feature to make a custom field for tasks only is also needed by my team. Please keep me looped in on any updates!

Basudha Sakshyarika

Thanks, @Ana Hughes. We’ll keep you in the loop on any updates. 👍🏽