Reccurent task
Hello,
When we add a reccurency to a task, the tasks CF are not filled with the value of the original task.... could it be the case? Thanks!
It looks like we don't have the translated page you're looking for, but we do have other content in English and offer support in English.
What can we help you with?
Learn. Share. Discuss.
Hello,
When we add a reccurency to a task, the tasks CF are not filled with the value of the original task.... could it be the case? Thanks!
Folllowing List for Post: Reccurent task
[this list is visible for admins and agents only]
Hello, you're correct. While the Custom Fields do carry over to recurrent tasks, the values inside the fields are not automatically pre-populated. Leaving the fields blank allows you to fill in data for each task. I would love to hear your use case for having these fields pre-filled in. I'm guessing that it's data that stays the same from task to task? If that's the case, does the data in the fields ever need to change?
Hi Stephanie -- for us, we're using the Effort Allocation beta, which comes in as a custom field, and when we create recurring tasks, we have to manually enter the effort again. Which isn't great when it's a weekly task and we're setting up tasks for all of 2018.
@Dana ahh I see, that definitely makes sense. Thank you!
Hi I have the same issue,
We use custom fields to define task types / Business units involved etc. and then use this data for categorizing & analyzing reporting.
I have a large number of daily tasks (running over long periods - up to a year) and we hence have to reenter all the custom fields values 1 by one, which is rather time consuming & can cause errors.
It would be great to be able to replicate custom field values when setting up a recurrence.
For me this is the main drawback of the tool, and rather frustrating.
Any chance to see this feature developed in the near future?
Hi all, the Product Team is interested in this idea. It's not currently on their schedule but it's something they'll be considering at a later stage. I'll keep you updated with any new information as I have it.
For now, please continue to vote on the original post and post use-cases/examples where possible 👍
We need this feature too.. Our weekly recurrent tasks mostly need the same values everytime, with the option to change them manually if needed. At the moment we have to manually enter all the default values everytime after a recurrent task is generated which is very time consuming. We used Asana before changing to Wrike and this is one of the features we miss the most.
We also would like to see this feature so that custom fields values replicated when setting up recurring tasks.
Hi @Stephanie Westbrook!
It would be really important to have this feature of replicating all fields of the task made recurrent. I honestly don't see value in not having these fields inherited. Even if we need to change them, we could change from the original setting rather than having it blank and entering the data. But generally, some custom settings are always the same for a recurring task.
Can you please kindly confirm that during the past 6 years, since this was flagged the first time, the Wrike team has tried to develop this feature?
Thank you!
Hi Monika Lontay, welcome to the forums 👋
Let me jump in for Steph here. At the moment, this idea is on the lower side of votes and not yet prioritized by our Product team. You continued feedback and upvotes on the original post helps our team estimate the amount of interest for different ideas here in the Product Feedback forum, so thank you for supporting this suggestion! We'll let you know if we have any updates here in the future.
In the meantime, please let me know if there's anything else I can help you with 🙂
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
Hi Lisa,
Having read the Upvoting rules, am I right to assume that all I need is to get the minimum threshold of 60 upvotes on the original post above this request considered?
Thank you
Hey Monika Lontay! You're right - the votes help our team gauge the interest for different suggestions, and once an idea reaches 60 upvotes, we ask our team to add one of the statuses. At the same time, we share and discuss feedback with less than 60 votes too. It's also important to mention that a higher vote count can't guarantee that our team will take a suggestion into work as it also depends on their priorities and resources. I hope this info helps!
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