[Status: Not planned] Include custom fields when making task recurrent

Hi Johan,

That sounds like a great idea!

Would it be acceptable to have the custom fields in the recurrence dialog instead of copying from the original task? From my understanding of the recurring tasks, the recurrence doesn't reference the "original task" but creates new tasks solely from the information in the recurrence dialog. Any tasks that are made off of the recurrence (including the first one) don't affect any future tasks in the recurrence.

Hi Johan & Joshua, thanks a lot for your ideas!

For now, this is not on the Product team's short-term roadmap; I'll get back to you if there's an update 🙌

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

Hey Johan and Joshua, this is currently not on the Product team's road map, I'll keep you posted if there are any updates. 😊

As a follow-up from Johns suggestion from April 04, 2019. This suggestion would be perfect, the custom fields is viable/editable on the reoccurring tasks. SUPER GOOD.

It's hard to see the reasons for this to be either hard to do for you guys OR that you prefer that the current solution is better.

Is it possible to have some kind of associated inheritance so the same custom fields can be showed but perhaps not edited in the reoccuring task ?

// Johan

Hi Johan Plate, sorry for the late reply.

I understand where you're coming from with this idea, it makes total sense! The fact that the suggestion is currently not planned doesn't mean that it will never be released - I'll keep you posted!

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 would like to add that this feature would be EXTREMELY important for our organization. I was actually shocked to find that it was not already a feature. I was wondering why my fields were not showing up in recurrent tasks. When can we expect this to be incorporated? 

mdr

Hi Ashleigh Hotz,

Thank you for sharing your feedback in relation to this suggestion, it's been shared with the Product team. As there are currently no plans to implement this at the moment, there is no ETA available. I'll be sure to keep you posted if there is any new information about this idea.

If you need anything else, be sure to let me know!

mdr

Hi, It's hard for us as customers to understand the Product Team. 

Why are there no plans for implementing this ? 

• Is it the wrong way ? (are there another workaround)
• Should we do this in another way ? (we do it wrong)
• It's not important compared to other development tasks ?

I would understand this if it was a completely new feature that was in some way obscure. But this feels like a completely viable idea. Based on your current data model, just a feature in a dialog/function that would help a lot. 

Why cant the custom fields be treated when copying the tasks ? 

Development 1. Be able to choose all custom fields or none from the parent task.  

Develpment 2. Be able to choose none, some or all custom fields from the parent task. 

Kind regards / Johan

mdr

As I am helping customers onboard Wrike, I can understand the comments made here.

Although I love all the new features Wrike is adding on almost a weekly basis, note that this new and often complex functionality often only attends to a relative small group of customers.

Imho Wrike should permanently reserve a percentage of its development capacity to improve existing features, often low hanging fruit, like the one mentioned here. Also because an improvement like this will be used by large parts of our customer base.

I would like to ask the Product Owner to consider my suggestion and to add this improvement to the next Sprint backlog.

Yes, to this date it has been two years since I first asked this. It's a showstopper for us in many use cases and I really can't understand whats the problem. I think I have a pretty clear picture of the datamodel behind the scenes, why is it so hard to fix this MINOR development comittment with a MAJOR improvement??? 

Thanx Arthur and Ashleigh and all the others that confirm the need of this feature.

// Johan

Wrike - what is the deal here? It's frustrating that this can't be prioritized when clearly your base would benefit from it. Can someone from Wrike help to make this more clear why it is not on the dev roadmap? It would be a HUGE time saver for me. 

Hello everyone! Thank you for sharing your feedback and support here on this thread.

Unfortunately, our team can't currently prioritize the recurrent task improvements, so this suggestion remains "Not planned" for now. We understand that this is disappointing news to you, but please rest assured that we will continue to pass on your feedback and regularly check for updates. We will let you know as soon as we have any news. 

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

Lisa, 

I wont give up this easy this time. 

You say that "you can't currently..." 

I'm asking WHY? 

Why can't you prioritize this ?? What is the product owner's saying in this, what is their answer? 

I also would like a follow upp answer to my earlier questions. 

• Is it the wrong way ? (are there another workaround)
• Should we do this in another way ? (we do it wrong)
• Is it impossible for you to solve this matter ?

Kind regards 

/ Johan

Hi Johan Plate, so sorry for the late reply here!

I can only share the Product status here, which for now remains "Not planned" due to other priorities. I understand that you're disappointed by the lack of this functionality and I'm really sorry to hear that.

We explain the details on how we and our Product team work with Product Feedback in this post. 

I'm sorry I'm not able to provide you with more info, and please rest assured your feedback is passed on to the Product team. 

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

Good morning - Just wanted to echo comments above.  We are planning to use Wrike predominantly for recurring tasks.  The fact that custom fields cannot be retained REALLY takes away from the efficiency and flexibility of the product for us.  Also, I see in other posts that this was first brought up in 2017 when you rolled out recurrent tasks.  I am a new user, so curious if there have been any improvements at all to the feature in the past 5 years?  Thanks!

Hi Crystal Torres, welcome to Wrike's Community 👋

First of all, thanks a lot for reaching out and sharing your use case here! Your feedback will be passed on to our Product team.

As you may know, our Product Feedback forum works off the voting system, and once a suggestion here gets 60 votes, we ask our Product team to add a status to it. At the same time, the team doesn't only look at these votes and comments, but also at other information like data and analytics, research outcomes, and reviews all of these elements together to determine if a suggestion should and can be worked on. That's why they can't commit to work on every suggestion that achieves the 60 votes threshold. Like in this particular case, the suggestion to include custom fields for recurring tasks isn't something that the team can work on right now due to other priorities. At the same time, Wrike is always evolving, so I'd suggest keeping an eye on all the Product announcements we post here on the Community. The easiest way would be to subscribe to our Weekly Release Notes to receive a weekly email with a link to the post where we announce all enhancements and fixes.  

I think it's also important to mention here that some of the suggestions from our members do get implemented by the Product team. If you'd like to learn more, I'd suggest checking out this wrap-up post on what's been released or worked on based on Community suggestions in 2021. 

I hope I was able to give you an overview of how we process Product Feedback here on the Community! 

In case you'd be interested to discuss your use case in more detail with a Wrike representative, please make sure to let me know 🙂

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

Has this moved up in the priority list? This is the biggest thing preventing us from tracking our equipment maintenance in Wrike. We need to sort and filter our equipment using custom fields like location in the lab, does the equipment fall under strict documentation regulations or standard regulations, etc. We can't use folders and subfolders to solve everything as we have a lot of parameters and this would get insanely complicated.

Hi Elizabeth Bevels, thank you for taking the time to share your use case and your feedback here. At the moment, this suggestion remains as "Not Planned" but we'll be sure to let you know if there are any updates in relation to this request 🙋🏻‍♀️

Hello,
This feature would greatly improve our user experience in Wrike. This will help ensure there are less blank custom fields with task reoccurences.

Hi Wrike Help Desk, thank you for chiming in here!

Hi - considering that all the reportring uses custom fields to help aggreagte data, it would be necessary for all tasks to have core values populated and flowing through the reurring task in the same manner as the blueprint tasks. This will help with ensuring there are less blank fields to manage on a manual basis. 

Hi all, this feature would be a great addition to recurring tasks as it would mean less blank fields and less time going back and fixing each task. 

Hi folks, apologies for the late reply here!

I've checked with our product team - this is not on their plans currently due to other priorities. We continue passing on your feedback and the vote count here, and if there are any changes in the future, we'll make sure to let you know.

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

Lisa  Please reconsider adding this to the priority list. Our team would really benefit from this. We need custom fields to use our analyze reports properly and this is a huge gap for us 

We need custom fields in recurring tasks to keep track of supply quantity and supply ordering. Unfortunately, the Wrike team hasn't added this to the priority list, and people have been waiting for over 4 years... Our company would highly benefit from having custom fields carry-over values. Please add this to the priority list. 

This has 81 upvotes... Why doesn't Wrike add it to the priority list based on the voting system?

I would love to see custom fields in recurring tasks. I am trying to use recurring tasks to track various renewal dates. I created a calendar view to quickly see when things are expiring, but it feels like a waste of time to continue with this approach since new tasks do not retain the custom field information put into the original task. I will have over 100 recurring tasks, but having to go through and update the custom fields every time a new one is created is too time-consuming and inefficient.

This would be an important improvement for us.Custom fields are what allows users to make clean Dashboards, Reports, and make use of the Automation tool. Without this function in the reoccurent tasks, we lose a huge amount of time, make mistakes because these reoccuring tasks don't show in our Dashboards/Reports, and basically force us to manually make tasks reocurring.

Please revisit this Wrike!!

More comments since I posted the other day. Hopefully, this gets revisited and chosen for planning.

As of last week, my company fully migrated our healthcare and operations team out of Wrike and into another software. We are now only using Wrike for marketing. The fact that custom fields do not stick to recurring tasks will impact the company's decision to resubscribe since we moved most of the company out of Wrike.

We needed this feature because we need to automatically find the sum of supplies per task for ordering. Without custom fields, we have no idea how many supplies to order for the week.

Thank you,

Naomi 

I'm going to jump on the bandwagon here... It seems like an obvious miss from the product design perspective.