What is the difference between Workflows "For tasks" and "For projects"
When I attempt to create a new project, I am given the option to select a Workflow. However, this Workflow is a "For tasks" type (as seen below in the second screenshot). The 401 Build a Workflow tutorial only demonstrates creating a "For tasks" Workflow. So what is a "For projects" workflow used for?
Brian Shotola you can create different workflows for tasks and projects. Tasks should be treated as individual action items whereas projects are treated as larger initiatives, usually clustering multiple tasks.
What you're setting in your first example within a project is just the default workflow that your tasks will adopt when you create tasks within that particular project. That isn't to say that it's set in stone! You can go into your tasks and change the workflow if needed as you create them. This is just setting the workflow they come in with by default.
In your second example/screenshot, you're just setting the default workflow for projects and tasks created in your space. So again, when you create a project or tasks in that Space, it will by default take on the workflow you set here for either work type. Again though, you can go in and change the workflow manually or set up automations to do so.
Welcome to the Community, Brian Shotola! 🙋🏻♀️
As Anna mentioned, workflows can be applied to both tasks and projects. Task workflows manage individual task statuses, while project workflows manage the overall project status.
If you have projects within a folder or nested, you can access project workflows in the Table view's Status column. For standalone projects, you can open them and click the "Info" option next to its name to open it in item view and access project workflows under Status. You can find more details in our Help Center articles. Does this answer your question?
Please feel free to share any follow-up questions or let me know if I misunderstood your question. 😊
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen
Basudha Sakshyarika Wrike Team member Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen
Ohhh I get it now. A Project Workflow is the workflow for the Project type. Task workflow for Task type. I was thinking the project workflow was the workflow applied at the Project level to which each Task in the project must follow. I am trying to wrap my head around Wrike as your model is VERY different from most. Everything in Wrike is basically its own independent entity that may or may not be associated through tags. Basically Tasks don't actually belong to a Project/Folder, they are just tagged as associated so each Task can have its own workflow. Thus a Project is its own entity that can have Tasks tagged to it, but independently has its own Workflow. Got it, thanks!