I found the following documentation regarding allowlists in Jira Service Management:
https://support.atlassian.com/jira-service-management-cloud/docs/manage-your-allowlist/
Currently, allowlists only support exact domain matching. For example, adding example.com will match anyuser@example.com. However, it won’t match anyuser@example.com.au or anyuser@mail.example.com.
The allowlist does not currently support individual email addresses, wildcards, or pattern matching.
I would like to ask:
Is there an existing feature request or plan to support subdomains automatically when a parent domain (e.g. example.com) is added to the allowlist?
If so, is there any publicly available timeline or roadmap for when this functionality might be implemented?
If not, are there any recommended workarounds or best practices to achieve similar behavior with the current feature set?
Hi @David Losonczi ,
No specific feature request for auto-subdomain support, but check this related open issue for wildcard ideas: https://jira.atlassian.com/browse/JSDCLOUD-973—add your vote or details to push it!
No public timeline yet; last update was 2021.
For now, manually add each subdomain as a workaround, or use automations to monitor rejects.
Can you give me an example of this automation?
Do you know any addon which would enable this feature?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On point 1 and 2, no there are no action on this or any future actions tom implement this.
on point 3, add all required domains, there is no other option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.