Version 1.0.0

Version 1.0.0

Released: 10 Jul 2026

This is the initial general availability release of E-SignSeal — Contract Execution for Jira. Version 1.0.0 delivers the complete Phase 1 feature set for Forge-native contract execution inside Jira Cloud.

Added

Template Management

  • Rich-text template editor powered by TipTap with support for headings, lists, bold, italic, underline, and horizontal rules
  • Jira merge field chips for 12 standard fields: Issue Key, Summary, Description, Assignee, Reporter, Priority, Status, Project Name, Project Key, Issue Type, Created Date, and Due Date
  • Custom Jira field chips auto-populated from your site's custom field configuration
  • Template status lifecycle: Draft → Published (→ Archived)
  • Readiness Checklist modal on publish to catch missing name, empty content, and broken field references
  • "Create draft copy" action on published templates to enable revision without breaking the live version
  • Template filtering by status (All / Draft / Published) and type (NDA / Services / HR / Compliance)

Contract Sending

  • Three-step New Contract wizard: Template + Issue → Signers + Settings → Review + Send
  • Issue-linked contract creation: Jira issue selector populates merge fields and sets the PDF attachment destination
  • Parallel signing: all signers are notified simultaneously at send time
  • Configurable envelope expiry (1–365 days, workspace default settable in General Settings)
  • Per-contract and workspace-default reminder toggle

Signing Session

  • Five-stage signing session: Review → OTP → Consent → Capture → Confirmation
  • OTP just-in-time dispatch: 6-digit HMAC-SHA256 code sent to signer's Jira-registered email on demand
  • 5-minute OTP validity window and 3-attempt limit per session
  • Consent stage requiring full document scroll and explicit checkbox acceptance
  • Signature capture: Draw mode (canvas) and Type mode (name rendered in signature font)

Contract Lifecycle

  • Contract statuses: In progress, Completed, Declined, Expired, Voided
  • Per-signer status tracking: Pending, Viewed, Signed, Declined
  • Daily midnight UTC expiry check
  • Manual reminder dispatch (one per signer per 24-hour window)
  • Void action for in-progress contracts with required reason field

Sealed PDF Generation

  • Signed PDF with embedded signature images for all signers
  • Appended audit certificate page with SHA-256 document fingerprint
  • Automatic attachment to linked Jira issue on contract completion

Audit and Certificate

  • Tamper-evident, append-only audit trail recording every envelope event with actor, timestamp, and IP address
  • Human-readable signing certificate on the Certificate tab of completed contracts
  • CSV export of audit event log

Dashboard and Analytics

  • Dashboard with five KPI cards: Active contracts, Completed (90 days), Median cycle time, Expiring ≤ 3 days, Declined
  • Cycle-time bar chart broken down by template
  • Bottleneck signers panel ranked by pending-contract count
  • Needs-attention table (expiring soon, stuck, declined)
  • Recent activity feed
  • "Your turn to sign" banner for users with pending signing sessions

Administration

  • First-time onboarding wizard (4 steps: Welcome, Projects, Permissions, Done)
  • Settings: Projects tab, General tab, Auth tab (read-only OTP config), Permissions tab
  • Role management: Workspace Admin (automatic), Template Manager, Sender, Signer
  • Jira user and group assignment for Template Manager and Sender roles
  • Re-run onboarding from General Settings

Security and Compliance

  • All data stored exclusively in Atlassian Forge Storage — no external data transmission
  • Minimum OAuth scopes: storage:app, read:jira-work, write:jira-work, read:jira-user, manage:jira-configuration

Fixed

None — initial release.

Changed

None — initial release.

Known limitations in 1.0.0

  • All signers must be Jira users on the site. External email signers are not supported.
  • Signing order is parallel only. Sequential signing is not available.
  • Authentication is OTP-only. Password-based or SSO-based signing authentication is not available.
  • Templates cannot be version-controlled in-place — use "Create draft copy" to revise.
  • Bulk sending (one template to multiple recipient sets) is not available.