Custom Fields - Data in Different Tasks/Projects
Our team runs into the situation where for example our project of the Planning phase of an overall project we determine some data which is then inputted into a custom field within a task. The next dependency is in a different project/phase called Purchasing. The task here now needs that data from the custom field in the Planning phase task. Currently we have to copy and paste it into each task. Is there any way to carry custom field data to different tasks? Or perhaps a better way we should be doing this - rather than relying on using attachments. I would prefer to keep it in Wrike.
It's silly that a subtask doesn't have the ability to inherit custom fields. The methods posted as "work-arounds" are dubious.
agree with Lauren - in our situation we have folder level, a project level, and then a "sub-project" task. It's cumbersome to NOT have the data follow down levels. In other words if a custom field is entered at the folder level, it should carry down to the project level at a minimum. If a project doesn't use that data or has different data it could still be changed at each level.
I've added a yes to the original post in the hopes that this could be added to a future build.
This is definitely something our team needs. We work by creating subtasks for different teams to complete a full project.
It's very time consuming for us and our team, managers, etc, to keep having to copy and paste the same data to subtasks.
Thanks
Holly
This will be useful for our team :)
As new users to Wrike, this is one of the first things that we are looking for, particularly because Meeting Notes it appears are often stored as Subtasks & we'd like Custom Fields to trickle down as well.
This functionality is something the Product Team have been thinking about in regards to a larger collaboration update. It's a little too soon for specifics but this thread is helpful in steering those internal conversations. I'll make sure to keep you in the loop as new information is available. Thanks for bumping this post 👍
I really need to see custom fields from both the project and task in my reports.
We have a large amount of conditional custom fields that feed projects from request forms. None of that information filters to the task
So the custom fields are blank on my task report. Every custom field has to be manually updated in the task to make it to the report.
Is there any discussion around this ?
Stacey
Stacey Gill Munich Re
Hey Stacey 👋 Sorry for the delay getting back here.
Like many here, this a great use case and I've made the team aware of it. Unlike other examples here, are you simply looking for a reference to the Project's Custom Field, like a 'ghost field' to show on Reports for example or would you like the actual Custom Field entry in the Project to roll down into tasks?
Hello there,
Could you please provide an update as to whether this feature will likely be implemented soon? Our team would really benefit from this also!
Thanks
I would like an update in this errand. We are in great need of custom fields to be inherent in tasks that are recurrent.
Is there any update on this thread? Looks like multiple long threads are running on the same topic..
Hello, I also would love to see this feature created. I upvoted the original post...hopefully this is implemented soon.
Is there any update on this thread? hopefully this can be implemented soon.
Agreed, I need the tasks to inherit the project level custom fields. Some of the reports I need are useless because I would have to add a custom field to hundreds of tasks per week.
For example, I need to run a report on assignees (task level) working within a specific medical content area (custom field). It's impossible to filter by specific assignees at the project level, so I would have to add this data to 30+task for hundreds of projects each quarter.
My vote is to please make this a priority so I can actually get some use out of reporting. Right now my work around has been to turn custom fields into a folder and tag the group of projects I'm looking at to them so I can limit by parent folder in reporting. This is a highly tedious process that makes my Wrike folders messy and still creates reporting issues because of how the data is grouped.
This would be very very helpful to us as well. We are constantly copying data from our "Projects" into the individual tasks. Is there any update to this?
We need this to - to be able to report on specific tasks (which phase a project is in) on specific types of project (projects with specific types of values in a custom field) ... It's really frustrating that you can't report on projects AND tasks - it's either one or the other - and the only work around is to export everything to Excel and then do VLOOKUPs... crazy.
Hi everyone, sorry for the late reply here!
There are a couple of similar suggestions on this forum, like for example this one - https://help.wrike.com/hc/en-us/community/posts/360018897394-Cascade-Custom-Field-Value-from-Folders-Projects-to-Sub-Projects-Folders-Tasks. As it already has more than 60 upvotes, we regularly update it -at the moment, the team are considering that suggestion.
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
In our use case , it is required to copy data from Project level to various other tasks in Project which is completely wastage of time and efforts.
In my opinion , there should be provision to link or apply equate formula in custom field at Task level which shall refer to Project/folder from where data is to be copied.
Hi Rakesh Kakkar, thank you for sharing your use case! It's been passed on to the Product team.
Currently we have information that we post in the top level of the project that it needed as a reference for every task in the project. It would be so much better to have custom fields that populate in every task for a project. This would eliminate the need to jump out of the task and view the top level of project in order to get important references.
Hi Kristen Mullen, welcome to the Community 👋
Thanks a lot for supporting this idea! I'm passing your feedback to our Product team 👍 Please make sure to upvote the original post above if you haven't yet - the number of votes helps the team understand how popular the suggestion is. Here's more detail on that, but please let me know if you have any questions!
If you'd like to know what this Community has to offer, please check out our New to Community forum.
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
I vote for this function too. Data in a custom field is shared across multiple tasks.
Thank you for bumping this thread and supporting the suggestion here Jun Jet Davies! Please upvote the original post at the top of the page too if you haven't done so yet 🙂
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
These issues have been around for such a long time, any updates beyond "the team is considering it"? My usage requirement is exactly the same as Stacey's from 2018!
I have been trying to figure this out for hours.... Is it really still not an option?
Thank you all for your comments! I'm afraid we don't have any updates about this suggestion. However, I can see that this idea is close to receiving 60 upvotes 👍 I'm passing your feedback on to our Product Team and please rest assured that we will keep you informed if there are any changes.
Not having the ability to auto-populate the same custom fields of tasks within a project is a huge problem for us and causing significant issues. It is impossible to pull the proper data w/out having the information at every level but this is not possible without dragging hundreds of fields. To make matters worse, the system CLEARLY does not enjoy this either as it constantly freezes or just moves very slow when I do so. If anyone has any ideas, please let me know, otherwise, this might be a dealbreaker at this point for my team.