For now, my team created a custom "New Default Workflow" and just assigned it as the workflow for all main folders and projects in our workspace. The original setup takes some time, but we're able to fix the workflow and apply it to new projects created.
We've already implemented a workaround for the annoying fact that Default Workflow cannot be rename or moved from it's primary position. Now our workaround fails because Default Workflow cannot be set as Fixed. I have no idea why there is such a limitation. Moreover, I can't really find any documentation about this limit.
We have been looking for this solution, as we want all the teams to use the corporate workflow, new users are still using the Default that do not works for us... 😑
Hi Alexander,
For now, my team created a custom "New Default Workflow" and just assigned it as the workflow for all main folders and projects in our workspace. The original setup takes some time, but we're able to fix the workflow and apply it to new projects created.
Hope that helps!
Carolanne
We've already implemented a workaround for the annoying fact that Default Workflow cannot be rename or moved from it's primary position. Now our workaround fails because Default Workflow cannot be set as Fixed. I have no idea why there is such a limitation. Moreover, I can't really find any documentation about this limit.
We have been looking for this solution, as we want all the teams to use the corporate workflow, new users are still using the Default that do not works for us... 😑
I guess no update to address this request huh!!! Then there should at least an option to set an Custom Workflow as a default.