API - Integration with other services

Email This Issue provides two types of API components that makes it possible to integrate it with other addons or external services.
REST API
Send emails
The REST API is a RESTFul service method that will send emails. 
Parameter
Value
REST path
$JIRA_BASE_URL/rest/jeti/1.0/email
Request Method
POST
Request Headers
Content-Type:application/json
Authentication
What Jira REST API offers
See details in the documentation.
Request Body
Email parameters in JSON
Response
200: if email is composed and sent successfully
500: if an error occured while composing and sending the email
Request Body Json
Request Body must be a well formatted Json object with the following structure.
Request Body Json
1
{
2
"issue":"BD-1", 
3
"to":["[email protected]","admin","g:jira-administrators","r:10000"],
4
"cc":["[email protected]", "o:lead", "o:watchers"],
5
"bcc":[],
6
"emailSubject":"This is the email's subject as if the user entered it",
7
"emailBody":"This is the email body",
8
"addAttachments":"ALL",
9
"emailTemplate":"Acknowledge Issue",
10
"emailOptions":
11
  {
12
  "addToWatchers":"true",
13
  "replyToMe":"true",
14
  "mailAsMe":"false",
15
  "addComments":"true",
16
  "suppressCommentEvent":"true", 
17
  "emailFormat":"text",
18
  "commentVisibility":"g:jira-administrators",
19
  "richHtml":"false"
20
  },
21
"payload":{"pay1":"val1"}
22
} 
Copied!
Fields in the Json object are the following:
Important: Only the issue field is mandatory.
Field
Definition
Example
issue
Numeric ID of the issue, or Issue Key
10000 or TEST-1
to,cc,bcc
Array of recipients:
email addresses
Jira user names
Jira participants with prefix "o:"
group names with prefix "g:"
project role IDs with prefix "r:"
custom field IDs with prefix "cf:"


Participant examples:
o:me - current user
o:reporter - issue reporter
o:assignee - issue assignee
o:watchers - issue watchers
o:lead - project lead
Group examples:
g:jira-administrators
Role examples:
r:10000, where 10000 is the numeric ID of the role
Custom Field examples:
cf:customfield_10010
emailSubject
Email Subject


emailBody
Email Body


addAttachments
Specifies how to select issue attachments to be added to the email




 Value is one of:
ALL: all issue attachments
NONE: none of the attachments
LATEST: newest version of all attachment
ADDED_LAST: most recently added attachments
emailTemplate
Email template ID or name, email will be generated using this template.
If not given, the template selected in the issue's Context will be used.


emailOptions
Email options to control various aspects of the email.
addToWatchers: if true, JETI will add email user recipients as watchers of the issue
replyToMe: if true, JETI will set the current user's email address as the Reply-To header in the email
mailAsMe: if true, JETI will set the current user's email address as the From Address in the email
addComments: if true, JETI will add a comment to the issue.
suppressComment: if true, JETI will not fire an Issue Commented event
commentVisibility: if provided, JETI will secure the comment it adds to the issue.
richHtml: if true, JETI will interpret emailBody as a HTML content


1
"emailOptions":
2
  {
3
  "addToWatchers":"true",
4
  "replyToMe":"true",
5
  "mailAsMe":"false",
6
  "addComments":"true",
7
  "suppressCommentEvent":"true", 
8
  "emailFormat":"text",
9
  "commentVisibility":"g:jira-administrators",
10
  "richHtml":"false"
11
  }
Copied!
payload
Key-Value map of values that will be added to the Velocity Context used to generate email body.
Email template may refer to these values and may render them in the email.


Request Statistics
The REST API is a RESTFul service method that will return the number of email items from the audit log. 
Parameter
Value
REST path
$JIRA_BASE_URL/rest/jeti/1.0/email/stat
Request Method
GET
Request Headers
Content-Type:application/json
Authentication
What Jira REST API offers
See details in the documentation​
Query Parameters
1
issueKey - Key of the issue whose email audit log is queried
2
issueId - Id of the issue whose email audit log is queried
3
mailHandlerId - ID of the Email This Issue Mail Handler to limit the query to incoming emails processed by this handler
4
type - Type of the email items to query (either of OUTGOING, INCOMING_ISSUE, INCOMING_COMMENT)
Copied!
Response Codes
200: if email is composed and sent successfully
500: if an error occurred while composing and sending the email
401: if the calling user account is not authorized to request the details
Response Data
Number of mail items matching the query
Example
http://JIRA_URL/rest/jeti/1.0/email/stat?issueKey=<issue key>
Request Email Items from the Audit Log
The REST API is a RESTFul service method that will return email items from the audit log matching the query parameters. 
Parameter
Value
REST path
$JIRA_BASE_URL/rest/jeti/1.0/email/query
Request Method
GET
Request Headers
Content-Type:application/json
Authentication
What Jira REST API offers
See details in the documentation.
Authorization
Only those users may query the email items who are authorized to view them in the issue.
Query Parameters
1
issueKey - Key of the issue whose email audit log is queried
2
issueId - Id of the issue whose email audit log is queried
3
limit- Limit the number of email items to return (max 1000)
4
type - Type of the email items to query (either of OUTGOING, INCOMING_ISSUE, INCOMING_COMMENT)
5
from - Date emails were sent or processed after (required format is dd/MM/yyyy)
6
to - Date emails were sent or processed before (required format is dd/MM/yyyy)
7
source - Trigger of the outgoing email (either of OPERATION, BULK, EVENT, WORKFLOW, AUTOREPLY, TEST, API, PREVIEW)
Copied!
Response Codes
200: if email is composed and sent successfully
500: if an error occurred while composing and sending the email
401: if the calling user account is not authorized to request the details 
Response Data
JSON Array of email items matching the query
Example
http://JIRA_URL/rest/jeti/1.0/email/stat?issueKey=<issue key>
Response structure
1
[
2
{
3
"issueId": 22900,
4
"subject": "(IT-349) Új request by customer \"Hello WORLD\"",
5
"body": <email body>,
6
"to": <to recipients>,
7
"cc":<cc recipients>,
8
"from": <sender email address>,
9
"format": <email format>,
10
"actorUserKey": <user key>,
11
"type": <type of email item>,
12
"source": <trigger of the email>,
13
"date": <date and time the email was sent or processed>
14
},]
Copied!
Queue Statistics 
SINCE 9.0.0
Incoming Queue Statistics
Parameter
Value
REST path
$JIRA_BASE_URL/rest/jeti/1.0/incomingMailQueue/statistic
Request Method
GET
Request Headers
Content-Type:application/json
Authentication
What Jira REST API offers
See details in the documentation.
Response Codes
200: if email is composed and sent successfully
500: if an error occurred while composing and sending the email
401: if the calling user account is not authorized to request the details
Response Data
Returns statistics of the incoming mail queue.
1
{
2
"new":<number of items with status NEW>,
3
"failed":<number of items with status FAILED>,
4
"skipped":<number of items with status SKIPPED>,
5
"processing":<number of items with status PROCESSING>
6
}
Copied!
Outgoing Queue Statistics
Parameter
Value
REST path
$JIRA_BASE_URL/rest/jeti/1.0/outgoingMailQueue/statistic
Request Method
GET
Request Headers
Content-Type:application/json
Authentication
What Jira REST API offers
See details in the documentation.
Response Codes
200: if email is composed and sent successfully
500: if an error occurred while composing and sending the email
401: if the calling user account is not authorized to request the details
Response Data
Returns statistics of the outgoing mail queue
1
{
2
"active":<number of items with status ACTIVE>,
3
"error":<number of items with status ERROR>
4
}
Copied!
Mail Generation Queue
Parameter
Value
REST path
$JIRA_BASE_URL/rest/jeti/1.0/mailGenerationQueue/statistic
Request Method
GET
Request Headers
Content-Type:application/json
Authentication
What Jira REST API offers
See details in the documentation.
Response Codes
200: if email is composed and sent successfully
500: if an error occurred while composing and sending the email
401: if the calling user account is not authorized to request the details
Response Data
Returns statistics of the mail generation queue.
1
{
2
"totalQueued":<total number of events that was ever queued>,
3
"totalCompleted":<total number of events completed>,
4
"currentlyOnQueue":<total number of events currently on queue>,
5
"activeWorkerThreads":<total number of active worker threads>,
6
"maxWorkerThreads":<max number of worker threads>,
7
"avgTimeInQueue":<average amount of time (ms) events spend on the queue>,
8
"maxQueueSize":<maximum number of events on the queue>
9
}
Copied!
OSGi Component API
In case, your Jira add-on wants to use Jira Email This Issue's email capabilities, you can build an integration between your add-on and Email This Issue. In order to do that you have to import the OSGi component Email This Issue publishes and call its methods.
API
Explanation
Component interface
1
com.metainf.jira.plugin.emailissue.api.EmailService
Copied!
Component method


1
void sendEmail(com.metainf.jira.plugin.emailissue.api.EmailDefinitionApi emailDefinition) throws Exception
Copied!


Component method


1
Collection<EmailLog> queryEmailLog(com.metainf.jira.plugin.emailissue.api.EmailLogQuery emailLogQuery) throws Exception
Copied!


Email Parameters
1
public class EmailDefinitionApi {
2
    private String issue;
3
​
4
    private List<String> to; //user keys and email addresses
5
    private List<String> cc; //user keys and email addresses
6
    private List<String> bcc; //user keys and email addresses
7
    private com.metainf.jira.plugin.emailissue.action.EmailOptions emailOptions;
8
    private String emailBody; //email body (will be injected in the template)
9
    private String emailSubject; //email subject (will be injected in the subject part of the template)
10
​
11
    private List<String> attachments; //issue attachment IDs
12
    private String addAttachments;
13
    private String emailTemplate; //name or ID of the Email template to use
14
    private Map<String, Object> payload; //arbitrary values that are injected into the Velocity Context in the template
15
}
16
​
17
public class EmailOptions {
18
	private boolean addToWatchers; //add recipient users to watchers, default: false
19
  	private boolean replyToMe; //set the current user as the reply-to address, default: false
20
  	private boolean mailAsMe; //set the sender address to the current user's email address, default: false
21
  	private String emailFormat; //email format "text" or "html"
22
  	private String emailPriority; //HIGH, NORMAL, LOW
23
}
24
​
25
public class EmailLogQuery {
26
	private Long issueId;
27
	private String issueKey;
28
	private String type; //EmailType
29
	private String source;
30
	private int top;
31
	private Date from;
32
	private Date to;
33
}
Copied!
nFeed
Next - Documentation
Administration
Last modified 6mo ago
Copy link
Contents
REST API
Send emails
Request Statistics
Request Email Items from the Audit Log
Queue Statistics
OSGi Component API