Anonymous Orca: Hi Stewart, any particular reason why you can't use labels for this? Types are currently fixed but labels are custom.

Sarah Hum: We use the Labels to differentiate between our different products.

Anonymous Orca: I see, I guess I'm not convinced that this should be a type any more than it can be a label. I would recommend trying the label route to see if that works for you.

In that sense Sarah Hum are you saying that it's not likely you'll be able to add your own Types full stop? So in my original example, I suggested being able to create "Coming Soon" or "Announcement".

I keep labels specifically for features of our platform. For consistency, if I were to start creating labels that were for topics such as "coming soon", filtering them would not be consistent.

For our team, we see Types as "types of announcements" and labels as "specific features that fall within the announcement type".

Otherwise we'd start having things like "Feature X" and "Coming Soon" as labels which would break consistency.

Wooden Dinosaur: Nope, not saying that. As with everything, we want to make sure there's a strong case for it before prioritizing anything. I actually think your examples make sense as a type. That said, I'm not sure we should allow completely custom types. For example, we could consider just adding a new "announcement" type.

We tend to err on the side of being prescriptive where we can.

Thanks for the reply Sarah Hum.

Absolutely, can't jump at every feature request. I think adding an additional fixed type would still be limiting when that moment arises where each of us want to add our own title, we all work differently after all.

This isn't a show stopper for me by any means, but certainly a nice to have. Adding new types would just give us flexibility in our announcements. Perhaps one for down track :)