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

Hi, love your function of making a task recurrent. 

Please add the posibility to include the custom-fields from the master (original) task. 

Upvote 71
14 comments
Spot On Innovative Approach Stellar Advice
Avatar

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.

16
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Hugh

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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Hugh

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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

2
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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.

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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. 

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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

0
Comment actions Permalink

Folllowing List for Post: [Status: Not planned] Include custom fields when making task recurrent
[this list is visible for admins and agents only]

Top
Didn’t find what you were looking for? Write new post