eSign supports import of external signature data into Jira Cloud. This function is available to Jira Administrators only. With this capability signatures captured in legacy external systems or other legacy Jira apps can be uploaded to and be visible within eSign.
Extract the legacy signatures into one or more .CSV files. Update or refine data as required to meet eSign requirements below.
Access the eSign Signature Import page in Jira Cloud under manage apps.
Load and Import the Signatures into existing Jira issues.
Access the Jira issues to view the imported Signatures.
Standard .csv files are supported. A header row is required with the following mandatory and some optional fields as follows:
Column Header | Required | Length | Example | Description |
|---|---|---|---|---|
Issue key | Yes | 16 | ABC-123 | Jira Issue Key |
Name | Yes | 50 | George Washington | Name of signee |
Title | No | 50 | Former President | Title of signee |
Meaning | No | 16 | Approval (Default) | Meaning of signature |
Date | Yes | 16 | Jan 01, 2020 | Date of signature (string) |
Time | No | 10 | 12:34 PM | Time of signature (string) |
Timezone | No | 16 | US/Eastern | Timezone of signature (string) |
Fields can be in any order within the CSV file; the header must match exactly including case. (e.g. “Name”, not “NAME”, or “name”)
Date and Time fields are string values and not interpreted
Additional fields/columns are ignored
Delimited is comma “,”. Values must be quoted if they contain commas.
Issue key,Name,Date,Time,Meaning,Title,Timezone,Extra DOC-100,George Washington,"Aug 2, 1776","12:45 PM",Approved,"President","US/Eastern","extra data ignored" DOC-100,Benjamin Franklin,"Aug 2, 1776",,Approved,"Inventor", DOC-100,Thomas Jefferson,"Aug 2, 1776",,Author,, TREATY-19,Ramsay MacDonald,"June 28, 1919","23:00",Approved,British Prime Minister, TREATY-19,Georges Clemenceau,"June 28, 1919",,Approved,French Prime Minister, TREATY-19,Francesco Saverio Nitti,"June 28, 1919",,Approved,Italian Prime Minister, |
The Jira Cloud issues must exist prior to importing signatures.
Multiple signatures may be imported to the same issue.
Imported signatures are appended onto existing imported signatures.
To preserve signature integrity, external signatures may not be imported onto issues where native executed eSign signatures already exist.
Imported Signatures can not be verified by eSign because the issue state at time of signature is not known.
Maximum size of an import file is 1,000 signatures that can be imported in a single session. If more signatures are required, split them into multiple CSV files.
The Signature Admin function Reset Signatures can be used on imported signatures to remove imported signatures from issues.
