JQL Functions are provided to search for issues against the Email Audit Log.
| Status | ||||
|---|---|---|---|---|
|
Search for issues created by email
Usage in JQL: issue in createdByEmail(senderEmailAddress,dateFrom, dateTo, containingText)
Parameters are optional:
- senderEmailAddress: email address of the sender of the email.
- dateFrom, dateTo: these are date values in format of dd/MM/yyyy (as 31/03/2014) or durations like 5d or 3h, etc.
- containingText: search the email subject for substring, you can use SQL wildcards like ? and %
Search for issues commented by email
Usage in JQL: issue in commentedByEmail(senderEmailAddress,dateFrom, dateTo, containingText)
Parameters are optional:
- senderEmailAddress: email address of the sender of the email.
- dateFrom, dateTo: these are date values in format of dd/MM/yyyy (as 31/03/2014) or durations like 5d or 3h, etc.
- containingText: search the email subject for substring, you can use SQL wildcards like ? and %
Search for issues sent in email
Usage in JQL: issue in sentInEmail(searchParams)
The parameter is a construct of multiple fields. The parameter itself and its fields are optional.
Fields in Search Parameter
| Field | Description |
|---|---|
| to | recipient to which the email was sent, SQL wildcards allowed |
| cc | copy recipient to which the email was sent, SQL wildcards allowed |
| bcc | blind copy recipient to which the email was sent, SQL wildcards allowed |
| sender | Jira username or email address of the sender |
| dateFrom | date in format of dd/MM/yyyy (as 31/03/2014) or durations like 5d or 3h, etc. |
| dateTo | date in format of dd/MM/yyyy (as 31/03/2014) or durations like 5d or 3h, etc. |
| source |
|
| subject | subject of the email that was sent, SQL wildcards accepted |
| issue | key of the issue that was sent |
| Note |
|---|
|
Examples
...
| Expertisefinder redirect | ||||||||
|---|---|---|---|---|---|---|---|---|
|