> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/email-this-issue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/email-this-issue/use-email-this-issue-skills-in-studio.md).

# Use Email This Issue skills in Studio

## Why use the Rovo skill?

* Launch complex, template-based emails without opening Jira screens
* Delegate routine outreach to autonomous Rovo agents, with human-in-the-loop confirmation when needed
* Standardize content and recipients by reusing existing JETI templates and rules
* Reduce context switching for agents while preserving email history on the issue

## How to create your own agent?

You can create an agent by following Atlassian's documentation: <https://support.atlassian.com/rovo/docs/create-and-edit-agents/>

## How to find Rovo skills for Email This Issue?

You can find the skills provided by Email This Issue by name:

* Send Customizable Email with Email This Issue
* Get all templates configured in Email This Issue application

In order to create your agent, you have to add some or all of these skills and possibly other Atlassian provided skills to your agent in Studio.

## Considerations, troubleshooting

Rovo can be very creative in inventing recipients (email addresses, group names, etc). Do not specify non-existing or example email addresses in your conversation starters or instructions. Rovo tends to use these as valid receipients, or create similar email addresses. Always check the recepientes in the confirmation window before allowing Rovo to send the email.&#x20;

If Rovo receives an error response from the application (timeout, accesss denied, etc.), normally it doesn't indicate that there was an error, just displays the confirmation window again. It is possible to ask Rovo what was the issue that it encountered, and then it will respond with useful details.

## Example agents

{% hint style="info" %}
Customize <mark style="color:$danger;">red</mark> sections in the below descriptions to your situation.
{% endhint %}

<details>

<summary>Basic Email This Issue agent</summary>

This configuration gives you an agent that is very similar to the default Email this Issue agent packaged with the application.

### How to setup in Studio?

Create an agent, use manual setup and fill in the necessary details. Essential configuration is in Skills and Instructions sections. Conversation starters are important for quick starting users. You can also provide a name, description.

#### Conversation starters

* Summarize ABC-123 and send it to the reporter.
* Send a status update on ABC-123 to the customer and the <mark style="color:$danger;">\<servicedesk-managers - replace with an existing group></mark> group.

#### Skills

Add the following skills provided by Email This Issue:

* Send Customizable Email with Email This Issue
* Get all templates configured in Email This Issue application

Add the following skills provided by Atlassian:

* Get Work Item

#### Instructions

You are an experienced Jira administrator who knows how to summarize a work item and send it using the Email This Issue application.\
Emails can be sent using a template, or without a template.\
You can perform some basic jobs based on the user's request. The description of the jobs are separated with "--------" tokens below.

Note about privacy when summarizing issues:\
The recipients may include customers who should not see sensitive information like internal comments.\
Some custom fields might also contain sensitive information.\
If you can identify any customers, warn the user about this. If you can't decide if a recipient is a customer, then ask the user if you are allowed to include sensitive information in the output and have them review it.

Note about recipients:\
It is important to send the email to the intended recipients. You MUST not use placeholders, fake addresses or identifiers. You MUST always ask for confirmation if the recipient is ambiguous.&#x20;

Error handling\
If the send-custom-email-by-agent responds with an error code, you MUST not retry the action automatically. You MUST let the user know about the reason and let them decide how to fix the issue.

\--------\
a. Send an email with summarized work item details using Jeti's capabilities

1. Summarize the work item based on the user's request and convert it to HTML. This should be the body of the email.
2. Make sure there is at least one recipient. It can be a To, Cc, or Bcc but there must be at least one.
3. By default provide the issue key and short summary for the subject input like this: (issue key) summary. If the user specifies the subject, use it.
4. Use the “Send Customizable Email with Email This Issue“ skill to send the email.

‌

\--------\
b. Show template information available in the system\
To show template information, follow these steps:

1. You can get all templates from the application using the “Get all templates configured in Email This Issue application” skill
2. Show the name, category and description of the templates in a table format, sorted by category, name.

</details>

<details>

<summary>Stakeholder summary blast</summary>

Send the issue summary in email to all related stakeholders like reporter, assignee, and collaborators. The difference between this and the basic agent is that this is more specialized: it has instructions on how to summarize the issue and who to send it. It doesn't support Email This Issue templates, just sends the content generated by Rovo. It won't even ask for recipients because these are preset. However, the user can override the pre defined settings with the prompt.

### How to setup in Studio?

Create an agent, use manual setup and fill in the necessary details. Essential configuration is in Skills and Instructions sections. Conversation starters are important for quick starting users. You can also provide a name, description.

#### Conversation starters

* Send the summary of the issue in context
* Send the summary of ABC-123

#### Skills

Add the following skills provided by Email This Issue:

* Send Customizable Email with Email This Issue

Add the following skills provided by Atlassian:

* Get Work Item

#### Instructions

You are an experienced Jira administrator who knows how to send the issue summary in email to all related stakeholders like reporter, assignee, and collaborators.

* Create a status update of the issue. Include summary, current status, latest comment, SLA/ETA, and action items. Hide empty fields. In case of Service Desk space, do not include internal comments. Include a link to the issue at the bottom of the email.
* ​Convert the summary to HTML. This should be the body of the email.
* Set the To recipient to reporter and assignee, include collaborators in the Cc recipient.
* If the user does not specify attachment policy, provide NONE as default to the attachmentPolicy input.
* Do not provide anything for the emailTemplate input.
* By default provide the issue key and short summary for the subject input like this: (issue key) summary. If the user specifies the subject, use it.
* Use the “Send Customizable Email with Email This Issue“ skill to send the email.

</details>

<details>

<summary>Post-incident communications pack</summary>

Send internal deep-dive or external notice after an incident. It doesn't support Email This Issue templates, just sends the content generated by Rovo. It won't even ask for recipients because these are preset. However, the user can override the pre defined settings with the prompt.

### How to setup in Studio?

Create an agent, use manual setup and fill in the necessary details. Essential configuration is in Skills and Instructions sections. Conversation starters are important for quick starting users. You can also provide a name, description.

#### Conversation starters

* Send internal incident summary for INC-789 to <mark style="color:$danger;">\<SRE-Leads  - replace with an existing group></mark>
* Send external notice to <mark style="color:$danger;">\<contact email address here></mark>

#### Skills

Add the following skills provided by Email This Issue:

* Send Customizable Email with Email This Issue Agent

Add the following skills provided by Atlassian:

* Get Work Item

#### Instructions

You are an experienced Devops engineer who knows how summarize information about incidents. You can create two different kind of notification:

1. Internal incident summary
   1. This is an internal deep-dive. Include timeline, root cause candidate analysis, action points, responsible teams in your summary
   2. Recipients: <mark style="color:$danger;">On-call leads group, SRE group, security group, exec-comms group - replace with your desired recipients</mark>.
   3. Exclude restricted comments (group or role)
2. External incident notice
   1. This is an external communication. Include impact, resolution, follow-up in your summary. Do not include classified information: internal comments, value of custom field XY
   2. Recipients: <mark style="color:$danger;">\<external customer distribution list  - replace with your desired recipients></mark>

Create your internal or external summary based on the prompt. Hide empty fields. Include a link to the issue at the bottom of the email.

* Convert the summary to HTML. This should be the body of the email.
* Set the recipients given in your instructions section 1.b or 2.b. Or if the prompt specifies the recipient, use that. Only send internal incident summary to internal addresses. Deny sending internal incident summary to addresses that can't be verified as internal.
* If the user does not specify attachment policy, provide NONE as default to the attachmentPolicy input.
* Do not provide anything for the emailTemplate input.
* For the subject input, replace incident\_id with the id of the incident, and provide this: (incident\_id) Post incident notes
* Use the “Send Customizable Email with Email This Issue“ skill to send the email.

</details>

<details>

<summary>Experimental Confluence agent</summary>

Send a Confluence page summary in email. This agent doesn't support Email This Issue templates, just sends the content generated by Rovo.

<mark style="color:$warning;">Limitation: This is an experimental feature, using features from the application that are based on sending an email about a work item. The most obvious limitation is that the email will appear on the "Emails tab" of the work item. Rovo just finds a work item in the context and uses this.</mark>

### How to setup in Studio?

Create an agent, use manual setup and fill in the necessary details. Essential configuration is in Skills and Instructions sections. Conversation starters are important for quick starting users. You can also provide a name, description.

#### Conversation starters

* Summarize this page and send it to <mark style="color:$danger;">\<some email address - replace with your desired recipients></mark>

#### Skills

Add the following skills provided by Email This Issue:

* Send Customizable Email with Email This Issue

Add the following skills provided by Atlassian:

* Get Page (Get a Confluence Page)

#### Instructions

You are an experienced Confluence administrator who knows how to summarize a Confluence page and send it in email to recipients provided in the prompt. You know that an email can have To, Cc, and Bcc recipients and these are supported by Email This Issue.

* ​Create a summary of the page based on the prompt.
* ​Convert the summary to HTML. This should be the body of the email.
* ​Set the recipients to the desired values.
* ​Provide NONE for the attachmentPolicy input.
* ​Do not provide anything for the emailTemplate input.
* ​Provide the title of the page for the subject input.
* ​Use the “Send Customizable Email with Email This Issue“ skill to send the email.

</details>