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 “TBNamed Template advanced”
| Table of Contents |
|---|
Why Template values?
Default values set for fields in Jira will for most fields be picked up by our Add-In. But Jira can not know anything of the email you want to create an issue from. The template defines which data of the email will be filled into the fields of your issue. If a field would have had both a default value and a template value, the template value will override the default value, because we assume the specific information of the email to be more accurate than any generic default value set in Jira.
Default template
We condensed what we think all of our users will want into a default template. By default, this template only fills the most standard fields.
...
Have a Jira Service Management project selected.
You have “Request type” enabled. Creating an issue via “Issue type” can never create a customer.
You will see a “(new)” appear after the email address in the “On behalf of” field.
...