Issue trackers

Jira integration

Link voted feedback to Jira issues, and let Jira move the post on your board and roadmap when the work is done.

How it connects: Native
Included from: Starter
On Free: No

Workflows

What you can do with Jira

Configured inside Looph, with the setup steps on its integration page. Slack and Discord are on every plan, Free included; GitHub and Jira start on Starter, and Segment on Growth.

01From a post, create a Jira issue or link one that already exists, so engineers see the request, and if you choose the demand behind it, from the ticket.
02Each Jira status maps to a Looph status. By default an In Progress status moves a linked post to In progress and a Done status moves it to Complete, and you can change any mapping.
03When a linked post reaches Complete, its followers are notified like any other status change, so the loop closes without anyone having to remember it.

Native connection

How it works

Looph sits in front of Jira Cloud rather than replacing it. Customers post and vote on a board; the requests that earn a place in the backlog become Jira issues, and engineering keeps working where it already works. You connect Jira by signing in to Atlassian, and Looph then acts in Jira as the person who connected it, so it sees only the projects that person can see.

Jira stays the source of truth. Status flows one way, from Jira to Looph, and Looph never changes anything in Jira on its own: it creates an issue, links one or comments only when someone asks it to. Looph registers a webhook for live updates and also checks linked issues every few minutes, so a missed update still arrives. A post with several linked issues completes when all of them are done.

Because roadmap columns are statuses, a mapped status change coming from Jira also moves the card on your public roadmap. An optional comment on the issue, off by default, shows how many people voted for and follow the post, without names or emails.

Setup

Setting up Jira

1Make sure the workspace is on Starter or above. Connecting needs the Integrations permission, which the owner and admins have by default.
2Open Settings, then Integrations, and choose Jira under Issue tracking. Choose Connect Jira, confirm that Jira will act as you, then sign in to Atlassian and approve access.
3Choose the Jira site for this workspace, then add the projects posts can link to.
4Check Status mapping. Every Jira status starts with a default taken from its category, and you can override any of them. Optionally set the issue type and labels for issues created from Looph, and turn on Show demand on the issue.
5From a post, choose Create Jira issue or Link Jira issue. From then on the post follows its linked issues.

The steps above are the full setup. For custom workflows on top, see the API and webhooks reference.

Atlassian: issue statuses and status categories

Plans

Which plans include Jira

Plan availability for the Jira integration
Requires	Free	Starter	Growth	Business
GitHub, Jira and Zapier	No	Yes	Yes	Yes

Taken from the pricing table — compare every line on the pricing page. Members are free on every plan, and connecting Jira doesn't add a charge of its own: the plan price is the whole bill.

Questions