Custom fields in tasks and subtasks

I need a custom field that will only be applied to tasks, not projects and folders. Apparently, the only available options are to apply custom fields to:

Folders, projects, taks and subtasks
Folders and projects
Projects

Is there any way I could use a custom field on tasks, and avoid the same field being visible in the Project Panel?

The actual field is a checkbox called "Issue". I want to create a new task and mark it as an issue, so I can make a report of all issues in a project. But I dont want the Issue checkbox to be visible in the Project Panel.

Find more posts tagged with

Under review

Status: Under review

Comments

Permanently deleted user

Hi Jens, thank you for sharing this feedback! Is the main problem here overall related to the Custom Field just being visible in the Project Info and taking up space there?

Beth Narunsky

We have the same issue. Only use Tasks but need custom fields for each task created.

Lauren Cooke

Yes it would be nice to at least hide a field from the Project Panel like in table view you can hide columns, it would be nice for the project panel to mirror that.

It would also be great to just have custom fields on a task level.

Stephanie Westbrook

Hi everyone, thanks for your feedback here! I'm going to go ahead and move this post to our Product Feedback section so that others can upvote it.

Ty LaStrapes

I have the same need. 😁

Indran Naick

You could do this by adding a dummy folder with the fields you need in tasks defined and then just tagging the task to that folder. The tasks will then inherit those fields. Newish to wrike so I'm not sure about the implications, would be interested to know if anyone else used it this way.

Aljaž Gorjup

We have same issue: for example we have project (product) where we would need general product data (custom fields) and then tasks (delivery) with data for that specific delivery (custom fields). It would benefit us greatly if this would be implemented.

Ryan Okelberry

Definitely need this too! There are times when we want to track task-specific metadata. Would be a big plus. Another extension of this would be that I can only find a way to update a custom filed associated to a task from a request form. Why can't a request form also update custom fields that are only associated to the project or folder?

Permanently deleted user

I really like @Indran's workaround here - has anyone else tried this yet?

Tuomo Suominen

(This might be a slihgtly different request, but) I would need project level custom metadata to be inherited to task level. Currently, I use blueprints to create new projects, and I can only fill out project-level metadata at that point. However, I need to have that same metadata available on task level in order to run dashboards and reports on those tasks, so I now also need to fill out the custom fields on task level. It would be a great relief to have the (option?) to inherit project level custom metadata down to task level.

Al Sape

Yes fully agree, this would help get tasks more flexibility, the "issue" use case is similar to my use of tasks for Agile development, would similarly mark them as "bugs," etc. While I'm very happy Projects and folders can have custom fields, it would be nice if they also could not have them!

Thanks.

Antoine Ancelin

Hi, fully agree. We have the same need!

Nick Etten

I was surprised to learn that this wasn't a part of current functionality. I can create custom fields for projects; projects and folders; and projects, folders, and tasks; but I can't create custom fields for just tasks or just folders.

This would be great to have implemented For reporting and tracking purposes for our team.

Permanently deleted user

Hey everyone, thank you for all your feedback here! It's been passed on to the Product team. I don't have an update at the moment. If anything changes, I'll be sure to let you know.

Ryan Okelberry

This continues to be left out of improvements. My comment to this was 9 months ago. We adopted custom fields back with "old table" view originally when they came out. Then the only way to add a custom field was from the table view. It's now been interesting to learn how a task adds up all the custom fields that it could potentially have access to based on the folders the task may be tagged into. This can become a large list, if your custom fields have been set up on higher level folders. Tasks end up having custom fields that don't necessarily even apply. We've had to restructure our custom fields to be associated to the lowest level folders possible, so as to minimize the accrual of custom fields associated to a task, that it picks up from parent folders.

Elizaveta Bogdanova

Hi everyone! I've spoken with the team again, and they are planning to review the custom field logic. Once we have any updates, we'll make sure to get back to you. Thanks for sharing your feedback!

FRANK MARSHALL

Any update? This is needed.

Elizaveta Bogdanova

Welcome to the Community, @FRANK MARSHALL 🙂

I'm checking with the team now and I'll let you know once I hear back from them. Thank you for reaching out!

Angela Kennewell

+1million for this here too!! 🙏

Custom Fields from one set of tasks (with/without subtasks) being "infected" by the Custom Fields of other unrelated tasks within the same folder is SUPER frustrating.

Eg. in a "delivery" folder, a custom field from a "transport" task such as "driver license number" etc does not need to appear in "accommodation" tasks, and conversely, a "# of rooms" custom field does not need to be available/visible to users completing the "transport" task!! lol

Right now the only solution is to have a million granular folders just for the purpose of keeping a tasks' custom fields away from other tasks - not great.

Being unable to limit a custom field to the task level REALLY diminishes the usefulness of custom fields by a lot

Elizaveta Bogdanova

Hi everyone! I wanted to let you know that although I don't have an update from the team at the moment, we will be adding a Product status here as soon as this post reaches the 60 upvotes threshold 👍

Sebastian Nemetz

Unfortunately, this is open for four years now. I hope there will be some progress soon.

It should be possible to define custom fields on every(!) level (exclusively for folders, projects, taks, subtasks or any combination of those).

Sebastian Nemetz

Hi @Elizaveta Bogdanova

as this topic has reached the 60–votes–threshold some weeks ago, you may consider assigning a status for this topic.

Thank you!

P.S. As well for another custom field topic /hc/en-us/community/posts/360043433754-Order-of-custom-fields-in-the-folder-project-task-view 😊

Cansu Yetisgin

Hi everyone, apologies for our delayed response here.

I'm happy to share that our team is currently researching a solution that should be helpful with this use case. We've therefore updated the status here to 'Investigating'! 🕵️

We expect to share more detail about the upcoming release in early Q4 so keep an eye out on here and on our Weekly Release Notes for the news 👀

Bo Samreth

Thank you for investigating - any updates on making task-only custom fields?

Elizaveta Bogdanova

Hi everyone! We still consider this suggestion as under research. Some detail on this: our team has recently released Work Templates in Wrike Labs as an experimental functionality that is considered as the next generation of Blueprints. With Work Templates, you can define custom fields that are shown for the particular work item (task or project). Other custom fields (inherited) are also still available for such tasks but hidden under the "show more" section. It seems that this functionality will resolve the suggestion here, and we're happy to discuss this further 😊 Please let me know what you think!