Custom Workflows Shouldn't Reassign Primary Workflow

Summary:  I want the project/folder workflow to remain the same when I tag other folders to the project/folder.

Details:

1. Create project in folder where default workflow is assigned. Tasks created and reflect default workflow.

2. Tag to a different folder with a custom workflow. Now project's workflow is custom instead of default.

3. Project will not allow me to change the workflow back to default because the secondary parent folder (the one tagged after project was created and tasks assigned) has custom workflow selected.  

4. To test, I remove the tagged folder with the custom workflow, and the project returns to default workflow.  As soon as the tagged folder is added back, the custom workflow returns.

 

Wrike Help reports, "The workflow in the subfolders and subprojects is changed automatically to match the custom workflow set for the parent Folder."  And "was done on purpose to facilitate workflow alignment in the subfolders and subprojects".  I argue that the parent folder should be the first one that the project was added to and that tagging it to other folders shouldn't change the workflow.  How is the workflow prioritized?  What if I have a project tagged in three folders all with different custom workflows?  This seems like a bug to me.

Upvote 3
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Комментариев: 7
Avatar
Anastasia

Hi Clair, thanks for sharing your thoughts and experience! I checked in with our Product Team and while this logic was something we intentionally implemented at first, we're always open to change, and this is something the team is already discussing. It's not on the nearest roadmap, but it ties in with other workflow optimizations we're thinking about. Thanks again for taking the time to write this here!

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Agree with OP ... it seems helpful to allow a folder to contain projects with different workflows.  Would like to see the ability to have a default (as now) but that one could change per project, as needed.  These could be similar projects that potentially need a different approach.

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Stephanie Westbrook

@Michael Hi and welcome to the forums 😎. Just want to confirm that you also want the option to go back to Wrike's default Workflow?

Stephanie Westbrook Community Team at Wrike Wrike Product Manager Узнайте о самых популярных функциях Wrike и советах по его использованию

Stephanie Westbrook Wrike Team member Узнайте о самых популярных функциях Wrike и советах по его использованию

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Right...let's say you set the workflow for a folder.  Each new project would ideally take on that workflow but allow you to change that at any point.  

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Stephanie Westbrook

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Has anything been done to implement the idea of having the ability to apply different workflows for different projects in one Folder? 

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

+1 I agree with this thread and hope this is implemented.  Defaulting to the same workflow makes sense, but having the ability to change it only reasonable. Thanks for listening.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Custom Workflows Shouldn't Reassign Primary Workflow
[this list is visible for admins and agents only]

Вверх
Didn’t find what you were looking for? Write new post