Discrepancy between new statuses in the Default Workflow and Custom Workflow
While a task may be listed as "New", the appearance in the list view can depend on what workflow is being used. Again, from the list view, the Default workflow shows no status as all, while the custom workflow shows the status of "new".
Can the code in the Default Workflow be updated so that it behaves the same as the custom workflow?
Meshelle Loos SYKES
Meshelle Loos SYKES
@Meshelle This completely makes sense to me, raising it with the team. Thank you for point it out!
Agreed - I create team meetings for my team's tasks in Wrike and it would be hugely beneficial to have the default workflow behave the same way as our custom ones!
Here is a visual of how this is affecting my team (below). As you can see, the first three permalinked tasks do not show a status before them, but the last two do (new and in progress - the NEW one here is from a custom workflow). I would love for my agendas to be fully reflective of all tasks statuses.
It also just does not make logical sense to me why anyone would want the first status of the default workflow displaying any differently than a custom workflow anywhere... consistency is key IMO for these types of programs. No one at Wrike has been able to give me a reason why so far...
I would be curious on why the system would be created to not display the status of the default workflow. It would be extremely beneficial to be able to have one meeting that shows all members who is working on what and what the status is. This helps create a very visible work environment for all parties involved. Can we get the Wrike team to address this?
Even if there is a case for this inconsistency in views, the option to make it consistent should be available.