I'd like to search for issues that have been created by users with an email address containing "domain.com". I tried the following JQL statement:
reporter ~ "@domain.com"
Unfortunately, this results in the following error message:
The operator '~' is not supported by the 'reporter' field.
Is there any way to work around this? I'd like to have this functionality to only trigger a webhook URL when a user with a particular domain in its email address open the issue.
Hi Floris
The Atlassian Jira Toolkit Plugin which is available in OnDemand provides a custom field type "Domain of reporter"
Add a customfield of this type to your view screen ( to check it works) and make sure it has a text searcher
Regards
Dieter
Please make sure you reindex Jira after you add the custom field.
I recommed to make the field global so it's available in all projects
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for you help Dieter! I added the custom field with the free text search template and re-indexed Jira. Indeed the issues now have a 'Domain of Reporter' field populated. However, the JQL statement:
"Domain of Reporter" ~ "domain"
also returns
The operator '~' is not supported by the 'Domain of Reporter' field.
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.
Besides this problem wouldn't it be sufficient to search this field using the equals operator?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's strange the CONTAINS operator doesn't work. Will look into this deeper if the problem persists after reindexing and restarting Jira
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Reindexing and Restarting didn't help so i had a look in the source of the plugin and found that the searcher you can select isn't a free text searcher but indeed an exact text searcher. The source code in com.atlassian.jira.toolkit.customfield.searchers.DomainSearcher looks like
public class DomainSearcher extends ExactTextSearcher implements CustomFieldStattable ...
This won't allow ~ searches, just = searches. To support CONTAINS (~) searches it should be
public class DomainSearcher extends TextSearcher implements CustomFieldStattable
To me this looks like a bug in the plugin, at least the label "Free text ..." when selecting the searcher is misleading. You should report this in the projects issue tracker if using the exact text searcher isn't sufficient for you. It also helps to make the Atlassian support aware of this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anyway the way it is now the field also implements CustomFieldStattable which means you can include it in the statistics gadgets and create nice two dimensional statistics about your reporter domains. Not sure if that would also be possible with the TextSearcher
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.