Skip to main content

The ability to dynamically assign CTA owner as Task owner when creating a Playbook also seems to have been removed with the recent “Horizoning”

Here is how you could configure the Task owner before:

And in the new UI the same task shows “No Value”, and doesn’t allow selecting the same:

 

This was a very clever and clean feature, is there a reason why it was removed?

Oh no….this is a big oversight 😫 We always use CTA>Owner as our Task Owner...

Even more concerning is when you opt-in to change to the new playbook, it removes all of your Task owners that were CTA>Owner and sets them to No Value...


@Tomas Trijonis would you want this changed to an Idea so we can get votes to track how many other admins this impacts?


I’d argue this is a bug


Thanks @Tomas Trijonis for highlighting; I switched to the new UI last week, and have now reverted to the pre-horizonization version.  Note, the playbooks revert back to CTA owner in the old UI, so the data can’t be deleted, perhaps just not showing correctly in the feature.  Agree @bradley I’d say this is a bug, but 🤷


@Tomas Trijonis would you want this changed to an Idea so we can get votes to track how many other admins this impacts?

Sounds good!


Hi,

If we leave the “Task Owner” empty the value will still default to “CTA Owner”. 

However, we understand the label not showing up must be confusing.

We will fix this behavior to be similar to the older one.

Thanks,

Monica Patra


Hi,

If we leave the “Task Owner” empty the value will still default to “CTA Owner”. 

However, we understand the label not showing up must be confusing.

We will fix this behavior to be similar to the older one.

Thanks,

Monica Patra

I’m not going to argue against reverting it, but had this been called out and documented this probably would have been a non-issue. There could even have been help text next to “Owner” that says “Defaults to CTA Owner when no value selected”. The product gets very confusing when behaviors change and we get to collectively find out what they are on their own rather than actual changelogs when features “just get a UI update”.


Reply