[Status: Investigating ๐Ÿ•ต๏ธโ€โ™€๏ธ] 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.

Upvote 61
23 comentarios
Spot On Innovative Approach Stellar Advice
Avatar
Anastasia

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?

2
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

3
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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.ย 

ย 

2
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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.ย 

Stephanie Westbrook Community Team at Wrike Wrike Product Manager Infรณrmate sobre las funciones y prรกcticas recomendadas de Wrike

Stephanie Westbrook Wrike Team member Infรณrmate sobre las funciones y prรกcticas recomendadas de Wrike

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I have the same need.ย  ๐Ÿ˜

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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.

3
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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.

3
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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?

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

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

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

(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.

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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.

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi, fully agree. We have the same need!

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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.

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Hugh

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.

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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.

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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!ย 

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

1
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Any update?ย  This is needed.

ย 

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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!ย 

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

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

+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 :(

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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 ๐Ÿ‘

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

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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).ย 

2
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Lisa

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 https://help.wrike.com/hc/en-us/community/posts/360043433754-Order-of-custom-fields-in-the-folder-project-task-viewย ๐Ÿ˜Š

0
Acciones de comentarios Permalink
Spot On Innovative Approach Stellar Advice
Avatar
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 ๐Ÿ‘€

Cansu Community Team at Wrike Wrike Product Manager Infรณrmate sobre las funciones y prรกcticas recomendadas de Wrike

Cansu Wrike Team member Infรณrmate sobre las funciones y prรกcticas recomendadas de Wrike

0
Acciones de comentarios Permalink

Folllowing List for Post: [Status: Investigating ๐Ÿ•ต๏ธโ€โ™€๏ธ] Custom fields in tasks and subtasks
[this list is visible for admins and agents only]

Arriba
Didnโ€™t find what you were looking for? Write new post