Domain-based assignment enhancement

Development
1

Hiho,

we are currently heavily using the domain-based assignment feature in Zammad, since we have a lot of contact with Universities. Many of them use subdomains for their faculties and departments, and there the domain-based assignment does not apply.

So I want to enhance this feature to allow subdomain matching on a per-organization basis. There are two ways this could be implemented, and I wanted to ask the devs which one they prefer.

1. Add a new boolean

I could add a new field called include subdomains with a yes and no toggle. That field would be active and evaluated based on whether domain-based assignment is enabled or not.

2. Change the current boolean to an int with enum

This would implicate a change of the current field from a booleanto an int:

  • 0 = no = no
  • 1 = yes = yes
  • 2 = yes_include_subdomains = yes, include subdomains

Before I start working on this, what would be your preferred way of implementing this?

Best

Toni

2

There’s a feature request somewhere in this Community or on Github regarding Domain Based assignment. It doesn’t cover subdomains, but rather looks at “several different domains”.

I personally believe both would be good and important in todays time. However, I cannot decide.

Maybe @YetAnotherGerrit has an answer or at least opinion on that.

3

I think the best solution would be to allow multiple entries and wildcards. This way it could look like: zammad.org *.zammad.org

This would allow for most of the uses-cases.

Because another common example is that a company has several TLD’s as well.

2 Likes
4

I think the best solution would be to allow multiple entries and wildcards. This way it could look like: zammad.org *.zammad.org

So the domain field should accept multiple space or comma separated values then?

5

There is a UI element, e.g. used for operators, that does not need seperation characters:

grafik

This can be used here as well.

1 Like