Official package · Automation and infrastructure

Live Jira issue updates on your own pages

A Jira Cloud app that sends issue changes and new comments to your channels the moment they happen, so a customer portal, an app or a wall screen updates without polling the Jira API.

Hibira Realtime for JiraGitHub ↗

  • issue-created, issue-updated with the fields that changed, issue-deleted and comment-added, on jira-{projectKey} and jira-issue-{issueKey}.
  • Private channels, a list of projects to send, and people’s names left out unless you turn them on.
  • Built on Atlassian Forge: settings and the secret are stored in Jira, and the app only talks to Jira and your Hibira cluster.
  • No app needed for a single rule: an incoming webhook URL from your app’s settings works in a Jira Automation Send web request action.

Sign in to see these snippets with your own cluster host. Sign in

  1. Install

    git clone https://github.com/hibira-io/jira && cd jira
npm install
forge register && forge deploy
forge install --product jira --site your-site.atlassian.net

  2. Set it up

    Jira → Settings → Apps → Hibira Realtime
  App ID:  YOUR_APP_ID
  Key:     YOUR_APP_KEY
  Secret:  YOUR_APP_SECRET
  → Save → Send test event

  3. Use it

    const pusher = new Pusher('YOUR_APP_KEY', {
  cluster: 'hkg',
  wsHost: 'ws.hibira.io',
});
pusher.subscribe('jira-issue-SUP-42').bind('issue-updated', ({ issue, changes }) => {
  document.querySelector('#status').textContent = issue.status;
});

  4. Or use Jira Automation

    Hibira portal → your app → Settings → Incoming webhook URL
  Channel: jira-SUP   Event: issue-updated   → Create URL

Jira → Project settings → Automation → Create rule
  When: Issue transitioned
  Then: Send web request
    URL:    the incoming webhook URL
             (add ?pick=issue.key,issue.fields.status.name to send less)
    Method: POST    Body: Issue data

Before you start

  • The app secret is shown only once, when you create the app or rotate its secret. Keep it on your server, never in a browser or game build.
  • On the Free plan, list every origin your pages load from in the app’s allowed origins (http://localhost:3000 while developing, then your domain). "*" needs a paid plan.
  • Forge needs a free Atlassian developer account and the Forge CLI (npm install -g @forge/cli).

Use the app key from your dashboard; the secret stays on your server. Channels, events and authorization endpoints work exactly as they do with Pusher. Create your free account →