See https://support.esign-app.com for eSign Documentation and Support

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Error

The Jira API returned a security error when eSign attempted to edit issue [Issue Number]. Review project security settings and contact support if the problem persists. (403)

Cause

eSign for Jira (App) user does not have access to edit the issue. As eSign stores the signature data via extended properties on the issues, this problem prevents signature data or the attachments from being stored.

This error can be displayed interactively when a user is working with eSign, or when eSign is triggered via a workflow post-function

Things to Check

  1. Ensure the default Jira project role atlassian-addons-project-access has the following project permissions granted:

    • Browser Project

    • Edit Issues

    • Add Comments

    • Create Attachments

  2. Review the Jira workflow status properties and confirm that the property “jira.issue.editable=false” is NOT applied to any statuses. This flag will make the issue read-only for all users, including eSign. See Advanced Workflow Configuration for alternatives to locking down issues for end-users only.

  3. By default, end users with Edit access to issues in the project will be allowed to Sign and Invite from eSign. If eSign Advanced (Fine-Grained) Security option has been enabled, Jira users will need additional eSign specific permissions granted to them directly or via roles/groups in the project permissions. See Project Settings for the description of permissions.

  • No labels