- Wrike Business or Wrike Enterprise (in order to use custom fields)
- Wrike Integrate (paid add-on)
- Wrike custom text field named Wrike Integrate (available to tasks, used to distinguish new tasks vs. updated tasks)
- Wrike custom text field named Task Title Prefix (available only to projects, used to record the project-specific task title prefix that should be added to all tasks within each project)
When creating custom fields used in Wrike Integrate recipes, we share these fields only with our Wrike Admins, so other users can't see or change the value in these fields. Keep in mind that the user linked to your Wrike Connector in Wrike Integrate will also need access to these fields in order to see/update them.
This recipe will trigger only for new tasks, and will look for a Task Title Prefix up to 4 folder/project levels above the task. The first non-blank prefix value found will be automatically added to the task title.
Because this recipe triggers only for new tasks, it will work only if you create the task within the desired folder/project tree. If you create a task then move or tag it to another folder, this recipe will not update the task title.
This example recipe only traverses 4 levels of parent folders/projects to look for a task title prefix. If you use more than 3 levels of nested sub-folders in your projects, you will need to modify this recipe to handle your desired number of nested sub-folders.
Wrike Integrate recipe example
Iniciar sesión para dejar un comentario.