Custom task types - reinstate flexibility of order for incomplete/complete statuses

The modal for custom task types has been recently redesigned since its initial launch. Although it may appear to have a clearer UI by separating/grouping the incomplete / complete statuses, it has broken the possibility to mix a complete status within the list of incomplete statuses; something that the previous modal allowed for. :confused:

With the new modal, we are now forced to group all the Complete statuses at the bottom of the dropdown list, which I believe is a serious short-coming of the new modal design and I would suggest this ability is reinstated as it has broken several workflows for my customers.

In certain use cases, the completion status could come prematurely and not necessarily at the end of the workflow. The issue is that the dropdown list of statuses of a custom task type reflects the sequence of a workflow and helps the users move the task onto the next status or step of a workflow. If the completed status are all at the bottom, this breaks that user experience, that was previously available.

Before

Note the position of ‘Budget rejected’ which is right after ‘Budget approved’
(ignore the scribbles, it’s from an older screenshot that was marked up for another post)

Note the sequence of statuses within the dropdown followed a specific workflow. Budget rejected was an option positioned right after Budget approved:

Now (broken)

Note that the position of ‘Budget rejected’ has now been forced to move down, below ‘In development’

The sequence of statuses does NOT follow the specific sequence of the workflow.
‘Budget rejected’ has now been forced to move down, below ‘In development’

Kindly consider reinstating the ability of mixing completed statuses within incomplete statuses for custom task types. Thanks!

3 Likes

Agreed. As with Require team selection upon project creation I think forcing a choice rather than defaulting to a complete/incomplete status would ensure people make concious decisions.

1 Like

Agree 100% here @Richard_Sather - voted!

1 Like

Yes, completely agree. @Forum-team, Could you please escalate this to the product team? The new inability to order the menu of a custom task type is a serious constraint with a serious UX cost and has already broken workflows.

A secondary issue: Periodically existing functionality is changed or removed without any warning. Can this be improved please?

Thanks,

Larry

4 Likes

Hi everyone, thanks so much for sharing your feedback with us! Our product team is aware of this topic and the concerns you’ve raised. Improving custom task types is one of our current product priorities, and this update is included in our ongoing opportunities for enhancement. I’ll keep you posted as soon as there are any updates to share!

4 Likes