Multiple ticket state colours aren't possible, but why?

I was perusing the topics mentioned in the community summary newsletter when I found this comment in reply to someone’s tech assistance request. I rather thought what they wanted to do was neat and I was thinking of recommending it to my admin. However, one of the Zammad team posted this:

I’m wondering why Zammad only has two colours for ticket states and what the rationale was behind not making it possible for organizations to set their own colours for ticket states. I understand that there is a limit to how much one can customize one’s own UI for open source tools, but isn’t that kinda one of the benefits of using open source software?

In fact it has 4.

It’s just not implemented. Apart from different colors still have to be visible in the interface etc.

Ah, that’s right. I didn’t remember that green and red were possibilities because I see them the least often.

I do not understand what you mean by this. What does “apart from different colours” mean?

I mean Zammad -currently- as two views (legacy and upcoming desktop/mobile view) and light and dark mode. For custom colors, you’d still have to ensure that they’re visually visible good enough, because if they aren’t, then you could just not bother using colors.

I’ve seen very few use cases for using colors actually. But that’s my personal take on this, as I believe that there’s much more important stuff than state colors.

There’s also no feature request on this board for this… you may wanna add one if it is that important to you.

1 Like

Thank you for explaining that. I was confused because Apart from different colors still have to be visible in the interface etc. was missing a few words in the sentence and it didn’t make sense to me. Your full explanation was much easier to understand, thank you.