eSign for Jira 2023 Q4 Updates Status: RELEASED Released: 2023-10-08

Index

Signature Types (New) OCT 8, 2023

This update upgrades the Signature Meanings into a more flexible and configurable Signature Type. This provides the following benefits:

• Signature Types by default are available project wide for all issues. This is the default.

• Signature Types can be restricted to specific combinations of issue types and states. (e.g. Only Enhancements and Defects that are In Progress.

• Configure Signature Types to restrict what project role a user requires to execute the signature. A project role can be assigned to group(s) and/or user(s).

• Signature Types can be individually enabled/disabled. The sort order of signature types (e.g. in the signature meaning picklist) can be adjusted by editing the position. (Hint: Set position to 4.5 to sort between position 4 and 5.)

• Signature Types rules are also applicable to bulk operations (invites and signatures).

Restriction Rule Timing

1. Issue Type rules are enforced at Invite time. (e.g. If Compliance Review is only applicable to New Feature issue types, Compliance Review will not show on the invite dialog for other issue types).

2. All Signature Type rules are enforced at signature execution time.

   

Project Settings Automatically Upgraded

eSign will automatically convert existing project settings to the new signature type model. All signatures that are available today will continue to be available after the upgrade:

• Standard signature meanings will become open (unrestricted) Signature Types.

• Issue Type specific meanings will be mapped to issue type restricted Signature Types.

• Project wide status restrictions will be applied to all signature types.

It is recommended to review eSign Project settings after the upgrade if the team is considering using the new configuration options.

Signature Execution Usability OCT 8, 2023

a) For improved compliance, the Signature Meaning field now requires the user to explicitly select the Meaning if there is more than one available choice. Note if the user was invited to sign for a specific meaning that will be pre-selected.

b) The Meaning (if necessary) or Signature Pin field is automatically in focus when the dialog is opened to improve usability and keyboard navigation.

c) Errors encountered during signing now display inline within the the dialog.

Signature Invite Improvements NOV 4, 2023

Improvements to Signature Invites including:

• Unused Signature Invites are automatically cleaned up on Finalize of Signatures.

• The Invite dialog has been expanded to support up to 8 signature types.

• The Signature panel now shows how long each invite has been waiting.

  

Support for Multi-Role Signees NOV 4, 2023

For organizations that require the same person to sign for multiple roles in the same issue, it is now possible to configure eSign to allow this. Note that existing behavior is unchanged in that projects by default can only have One Signature per User (per issue status).

Embedded Image Rendering in Signature Archive PDF Report NOV 4, 2023

With this new enhancement (attached) images embedded into issue Description fields or Wiki formatted customer fields can now be rendered into the PDF Signature Archive reports.

Images of gif, jpg, and png up to 1 MB in size are supported. Larger images will be replaced with a thumbnail.

Email Notify on Invite OCT 8, 2023

It is now possible to configure whether eSign will send an email to invited users. By default email notification is enabled.

Voiding individual Signatures and Cancelling individual Invites DEC 21, 2023

New options to Void individual Signatures and Cancel Invites are available from the row menu (…) in the signature panel.

Void Signature

Void Signature is available to the signee, owner and admins. Note that only signature captured within the current Jira issue status can be voided. Finalized signatures can not be modified.

Cancel Invite

Cancel Invite is available to Signature owners and admins.

New Signature Admin Post Function - Cancel Pending Signatures DEC 21, 2023

A new workflow post function is available to Cancel Pending Signatures during a transition.

Additional Items

• Invite dialog - Prevent accidental submission with Enter key

• API Security improvements

• 2023-10-22 Address wrapping of custom fields with very long names in PDF archive

• 2023-10-22 Correct background color theming of signature panel table header

eSign for Jira 2023 Q3 Updates Status: RELEASED Released: 2023-07-21

Support the new Jira Dark Theme

eSign for Jira now supports both the traditional Light theme and new Jira Dark theme. Screens will adapt to the theme to align with the current Jira mode.

The option to switch Jira between Light and Dark themes is under the “Your Profile and Settings” menu > Theme..

Dark Theme

Light Theme

Workflow Post Function - Signature Invite by Group

Released 2023-06-18

The Signature Invite post function can now be configured to Invite By Group. With this option, all members of the Atlassian Group named will be invited to sign.

Workflow Validator - Required Signatures Group Search

Released 2023-06-18

The Signature Validator group selector was upgraded to provide a search function. This will allow customers with many groups (e.g. 100+) to attach them to the validator.

PDF Signature Archive

Released 2023-06-04

• Display of wiki rendered tables enabled for description and custom text areas.

• Custom field rendering added for “float”.

• Additional protection added for unsupported custom field rendering errors.

• JUNE 25 Notify user and project lead via email if the PDF signature archive report could not be attached to the issue.

Additional Items

2023-06-04 Content Security Policy enforcement enabled for eSign.

2023-06-04 Improved error messaging when Atlassian API requests time out (after 30 seconds).

2023-07-04 Fix issue with required signatures workflow validator expression not allowing a pass with empty group list configured.

2023-08-04 Fix issue with excessive notification emails when signature archives were not enabled for a project.

2023-09-05 Improve messages when eSign is not enabled for a project.

2023-09-14 Improve error message when eSign access is blocked by Jira project security settings.

eSign Document Management - New in 2023

In 2023 the eSign team released eSign Document Management for Confluence. If your team needs a comprehensive document review, approval, release workflow plus an integrated training module, powered by the eSign electronic signature engine.

View a 5 minute demo here: https://www.youtube.com/watch?v=kWjAzZRy2Wo&t=1s

eSign for Jira 2023 Q2 Updates Status: RELEASED Released: 2023-04-01

Contents

eSign Document Management

The eSign team has released a NEW app, eSign Document Management for Confluence. Take a look if your team needs a comprehensive document control solution that features the eSign electronic signature engine.

View a 5 minute demo here: https://www.youtube.com/watch?v=kWjAzZRy2Wo&t=1s

Added Integration with Jira Automation

With this update it is now possible to trigger Jira Automation rules via webhooks configured against eSign events. This will make it possible to automatically transition issues to a new status after signing, for example.

Enable the webhooks in eSign Project Settings. See the eSign Guide - JIra Automation Integration for more information and examples

New PDF Signature Archive customization options

As requested by a few customers, the PDF Signature Archive report can now be customized to show or hide Attachments and or Comments.

Default behavior is still to include all attachments and comments (unchanged). Adjust this in eSign Project Settings.

PDF Signature Archive - Improved Compliance Options

To assist with compliance to internal quality and regulatory departments, the following updates have been made to the PDF Signature Archive report:

1. The dates and time formats for all Jira standard and custom fields are now aligned with the regional and timezone context of the signature page. Previously custom Jira date and date/time fields sometimes were presented in different formats.

2. Standard and custom fields configured to display in the Archive report are now displayed as N/A if they are empty.

3. There is a new project setting to override all the date/time formats to be displayed in ISO 8601 format to address customers who require a full numeric and standards based date format in their formal documentation.

User Profile - Account Type added for JSM clarity.

The eSign User Profile now shows the Account Type field to assist with visibility and diagnosing issues on the Jira Service Management portal. The Account Type (Atlassian or Customer) determines how signatures operate within the portal.

Atlassian accounts have full signatures; the Execute Signature dialog operates the same way whether signing in the portal or within the Jira environment. These signatures are restricted by eSign Security settings (standard or advanced).

Customer accounts have limited signatures, they do not have a Pin and cannot choose a signature meaning. Customers accounts can sign any service request they have access to see.

Additional Items

• Improvements to some error dialog handling and formatting

• Security updates

• Technical library updates

• 2023-05-02 Minor layout adjustments to PDF Signature Archive report

eSign for Jira 2023 Q1 Updates Status: RELEASED Released: 2023-01-14

Contents

Signature Issue Type Restrictions and Meanings

It is now possible to choose which Issue Types (e.g. Epic, Enhancement, Task) in a project can have Signatures, and for each of those Issue Types configure an individual list of signature meanings (e.g. Dev Approval, QA Approval, Compliance Review).

Combining this option with Jira Issue Type specific workflows and eSign validators and post functions can allow customers to have very different approval paths for each issue type.

The Issue Type specific meanings are displayed in the Execute Signature , Invite Pages, as well as the bulk Sign/Invite options.

Configure the Issue Type restrictions in the eSign Project Settings page.

Extended Signature Verification for Built-in and Custom Issue Fields

In response to customer requests, we are please to announce that eSign for Jira has added support for Extended Signature Verification. With this enhancement, eSign can be configured to verify additional Jira built-in and/or custom fields have not been modified since signing.

In default field verification mode, captured signatures are checked against the issue Summary, Description, and Attachments. Now additional fields can be included with the signature verification. The issue history is searched for changes to any additional fields after a signature.

Globally Enable or Disable Signatures for all projects

For customers that have many Jira projects it is now possible to disable eSign for all projects, and selectively enable it for projects that require Signatures. Find this new option under Apps | eSign App Settings.

The eSign Project Settings page has been updated to make it clear what global setting is in place.