Helpmonks Logo
Underdog. Fast. Unfiltered.

Connect Helpmonks to Jira

The Jira integration is included with Helpmonks. You need a Helpmonks account and access to a Jira Cloud software or business project. Helpmonks supplies the OAuth application; you do not need to register an Atlassian developer app, create an API token or enter a client secret.

Open Jira settings in your US Helpmonks account or EU Helpmonks account.

  1. Sign in to Helpmonks as an administrator and open Settings → Extensions → Jira.
  2. Click Connect Jira, sign in to Atlassian and approve access to your Jira site.
  3. Choose a project and a top-level issue type. Complete any required field defaults. Jira must expose Description and Labels on the issue creation screen.
  4. Choose the mailboxes that may send conversations to Jira. Decide whether to include shared notes and attachments and whether to import Jira comments.
  5. Enable Jira and save. Open a conversation in an enabled mailbox and click Add to Jira, or add the Jira action to a Helpmonks workflow.

The connected Jira account needs permission to browse the destination project, create issues, add comments and attachments, and create issue links. You may connect a dedicated integration account. Jira records that account as the author of copied emails; each copy also names the original sender and date.

One conversation links to one issue. Its sidebar displays the issue key, summary, status, assignee and priority. Use Pause sync, Resume sync or Retry sync on that card. Normal synchronization runs approximately once a minute, including when the conversation is closed.

Existing and subsequent emails become Jira comments. Shared internal notes and their attachments can also be included; author-only notes are excluded. The customer's email address is included in the issue description and in a Jira label. Anyone who can view the issue can read the content sent to Jira. Each attachment must fit Jira's upload limit and be no larger than 50 MB.

With Import Jira comments enabled, existing and new Jira comments appear as read-only shared internal notes in Helpmonks. They are never sent as customer email. Helpmonks-origin comments and Jira comments restricted to a group or role are excluded. Jira attachment references link back to Jira; their files are not downloaded into Helpmonks.

Copies are append-only. Editing or deleting an original does not ordinarily change its copy. Jira status does not change the Helpmonks inbox status. Privacy removal is an exception: Helpmonks erases affected imported Jira comments and cached assignee identities when required by Atlassian's privacy reporting API.

Disconnect stops synchronization, removes the stored OAuth tokens, and removes imported Jira comments and cached assignee identities from Helpmonks. Original Helpmonks messages and issues or comments already sent to Jira remain. Disconnect is different from pausing sync or disabling the extension, which preserve existing copies. Reconnecting does not restore comments removed for privacy or by disconnect; new comments may be imported after sync resumes.

If authorization expires or is revoked, use Reconnect Jira in Extensions. If Jira rejects a field or a permission, correct the project defaults or Jira account permissions and retry the affected conversation. Contact Helpmonks through the support options in your account if the connection remains unavailable.

This release supports Jira Cloud software and business projects. Jira Service Management and Data Center are not supported.

Read Helpmonks for Jira: data and privacy for details about the information shared, retained and removed by the connector.

Bring everyone into the customer conversation.

Unlimited users. Shared inbox pricing. One place for customer context.

Book demo Start 30-day free trial