If a folder or project has a custom workflow, no child folder can have the default workflow.

Current Situation:

If a Folder/Project has a Default Workflow (for tasks) set, but is also tagged in another location where a Custom Workflow is applied, the Custom Workflow will indeed override the Default one. 

I.E. tagging a folder or project (a) which has the default workflow set to a folder (b) which has a custom workflow defined will automatically change the default workflow for folder project (a).

This does not occur if project (a) has any custom workflow assigned.

In other words: it is not possible to assign the default workflow to a project or folder (a) if any parent (b) folder has a custom default workflow defined.

The default workflow for (a) can be selected using the change-workflow function, but this will not take any effect.

Desired situation:

The default workflow should be treated like any custom workflow.

 

 

0
1 comment
Spot On Innovative Approach Stellar Advice
Avatar
Hello Andreas Günther, welcome to the Community 👋🏻
 
Thank you for sharing your use case and feedback with us. I've passed it on to our Product team. Here is a useful article explaining what happens after we receive Product feedback 🖊

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

0
Comment actions Permalink

Folllowing List for Post: If a folder or project has a custom workflow, no child folder can have the default workflow.
[this list is visible for admins and agents only]

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