On this page you will learn what the template in the admin section of our Jira app does and how it can help you improve your workflow. If you already know the basics and want to tweak even more, consider reading Template advanced - Outlook Email for Jira - yasoon (atlassian.net Configuring templates (advanced)
| Table of Contents |
|---|
Why Template values?
...
description: <BODY>
The body of the email will be filled into the description of the issue or the description-equivalent of the request.summary: <SUBJECT>
The subject of the email will be the summary of the issue.reporter: <SENDER>
This one is a little tricky. See in the dedicated section for Template basics | mapping-<SENDER> below.customfield_*****: <ORGANIZATIONS> (the actual custom field number depends on your instance and is determined accordingly)
If the reporter is found to be an existing customer, the organizations the customer is part of will be pre-filled.
...
You can decide how the fields of your issue will be pre-filled by adding a mapping for this specific field. If a mapping is not valid for a field it will in most cases be ignored and should not cause an error.
User specific mappings
<SENDER>
| Anchor | ||
|---|---|---|
|
...
|
...
|
This definitely is the most complicated mapping.
...
Otherwise, if the mapping is associated with the “reporter” field and all of the following are applicable, our Add-In is capable of directly creating a new customer, see also Why do new customers appear in my Jira Service Management instance? .
Have a Jira Service Management project selected.
You have “Request type” enabled. Creating an issue via “Issue type” can never create a customer.
...
Mappings that are valid for Text fields can also be included in text.
...
Additional resources
Template advanced - Outlook Email for Jira - yasoon (atlassian.netConfiguring templates (advanced)