Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Feature

Description

HTML Templates

When using Email function, you can use the rich text editor to format and also include images. Variable substitution is also supported so that any field on the issue can be pulled into the email body. Images can be included by clicking on the image icon. You can resize the images but note that some images may not display in this viewer due to restrictions to URL’s. However the images will still be rendered on the actual email that’s sent.

Variable Substitution

Variable substitution is supported so that any field on the issue can be pulled into the email body. Apart from the fields, here are reserved keywords that can be used:

{taskkey} - pulls the Jira issue key

{dynamic_prefix} - creates a random character string. This can be used in conjunction with Azure AD to create and send a one time password. See this link for more information.

Docusign Support

Emails sent using OnLink can include links to a Docusign document so that fields in the document are auto-populated by OnLink. In order to use this feature, first create a Docusign PowerForm based on your document template. See this link for reference: https://support.docusign.com/s/document-item?language=en_US&rsc_301=&bundleId=jbx1643062255110&topicId=uqn1578456644428.html&_LANG=enus

Once the power form is setup, you can map customfields from your Jira issue to the various input parameters. See this link for more info - pre-fill values in docusign.

Here’s a sample URL - https://{PowerForm URL}&Signer1_UserName={customfield_10010}&Signer1_Email={customfield_10011}&Address={customfield_10012}

Here’s a quick demo video showcasing this feature:

https://www.loom.com/share/f33cce2b46f4404b8c6e4397519b8271

Adobe eSign Support

Emails sent using OnLink can include links to a Adobe eSign document so that fields in the document are auto-populated by OnLink. In order to use this feature, first create an Adobe eSign web form based on your document template. See this link for reference: https://www.adobe.com/sign/features/web-forms.html

https://www.loom.com/share/4f15505e861849c387ded3470e6ce018

Once the web form is setup, you can map customfields from your Jira issue to the various input parameters.

Here’s a sample URL - https://{Adobe eSign Web Form URL}&Signer1_UserNamesecure.na1.adobesign.com/public/esignWidget?wid=CBF2s*#Branch_Office={customfield_1001010101}&Signer1Emp_EmailID={customfield_10011}&Address={customfield_10012}10102} (Reference)

Here’s a screenshot of Adobe eSign form:

image-20240513-170854.pngImage Removedimage-20240513-170854.pngImage Added