[Status: Launched! 🚀] Project workflows shouldn't be mixed with Task workflows
Please separate Project workflows from Task workflows. To have possibility to select Task oriented workflows only in Tasks and Project oriented workflows only in Projects
Current approach creates quite severe issues:
- Projects are created in Default folder Workflows which are reserved for tasks. As a result Tasks and Projects would have the same workflow in the folder by default - identification complication.
- Now we have dozens of workflows designed for tasks with predefined assignees and specifically locked transitions which confuse people within project status selection process - frustration issue.
- People may choose Project workflow in their tasks - longer list and miss selection issue.
- All widgets in all dashboards concerning projects will crash in case of wrong workflow selection.
- Table view filters can select tasks and projects as well - identification issue.
So please keep Projects and Tasks as separated entities as much as possible. Cause with mixed workflows there is no big difference between Project and Task with sub-tasks. That's quite messy.
P.S.: Locked workflows can't solve the issue cause some level of flexibility should be granted.
Agreed here! Would it be possible to also have a folder default with Project workflow and Task workflow? If we create a project that is grouped under a folder, it should follow the same convention as the project has the same project and task workflow as the others
Definitely supporting this. Combining the two workflow types makes no sense at all.
A project workflow will often be very different than the workflows the tasks go through. Just as it always has been but to improve what has always been is the ability to customize project workflows. Project worklfow. Task workflow. Thank you
Yup - this would be a great functionality addition
I just noticed that our recent projects have all been created with the Default Workflow we use for tasks, instead of the Project Workflow that used to be automatically assigned at the project level. I'm in the process of reviewing all our projects now to fix the project-level workflow on each.
When did this change happen?
Is there a way to specify the default workflow for projects?
I'm having trouble too. Even if I open a new Project, and choose the default workflow to be one of our custom ones instead of default, it still sets it up as the default.
It's a problem because we have to remind people to choose the right thing.
Indeed, distinct workflows for project and task is a must...! I'm waiting for this feature.
Meanwhile, a way to work with project workflow is to systematically create projects with a Request Form linked to a Blueprint project that has the right project workflow...
I'm confused. This functionality already exists in Wrike. I can set separate default task and project workflows at the space, project, and folder level in Wrike. I think I've had this ability for at least a few months now. I've included a screenshot.
Apologies, John Bibbs! Made a mistake when replying to this thread, sorry for any inconvenience caused.
It's true, this feature has been implemented to Wrike. I've deleted my comment and changed the status of this thread to Launched. If you have any further questions or feedback, be sure to let me know.
Is there a how-to on this functionality?
Hi Angela Kennewell! In space settings, you can set up workflows for tasks and for projects separately:
Does this help?
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
Yes, that is helpful. I will have a play around with it and come back to you if anything is unclear. Thanks!