Back to docs
Integration · ~10 minutes

Connect Jira Cloud to Mnueron Meet

Once connected, every action item Mnueron extracts from a meeting transcript can become a real Jira ticket with one click — assigned, labeled, and linked back to the meeting it came from. Live status reads pull the current Jira state back into the meeting detail page.

1

Sign up for Atlassian Cloud (free tier is fine)

If you already have an Atlassian Cloud site, skip this step. Otherwise visit atlassian.com/software/jira/free and create a workspace. The free tier covers 10 users and 2GB of storage — plenty for staging the Mnueron integration. Use your own personal email; you can invite teammates later.

Note your Cloud URL — it looks like https://your-team.atlassian.net. You'll paste this into Mnueron in step 4.

2

Create a project for Mnueron to write tickets into

In Jira, click Projects → Create project. Pick the Kanban or Scrum template — either works. Pick a short key like MNUE or DEMO; you'll paste this into Mnueron as the default project key so tickets created from action items land here by default.

You can connect more than one project; the default is just the fallback for clicks that don't specify a project.

3

Mint an API token

Visit id.atlassian.com/manage-profile/security/api-tokens → Create API token. Name it something descriptive like "Mnueron Meet" so you can revoke it independently later. Copy the value — Atlassian shows the token only once.

Atlassian Cloud uses email + token Basic auth. The email must match the account that minted the token. Mnueron asks for both in the next step.
4

Paste credentials into Mnueron

Open /account-settings/integrations/jira and fill in:

  • Atlassian Cloud URL — https://your-team.atlassian.net
  • Atlassian email — the email tied to the API token
  • API token — paste the value from step 3
  • Default project key — e.g. MNUE

Click Save and verify. Mnueron stores the token encrypted at rest (pgcrypto by default; KMS envelope on enterprise tier), then immediately runs a verify roundtrip against your Jira to confirm the token is valid. You'll see a green pill with your Atlassian display name on success.

The verify call is GET /rest/api/3/myself— a read-only ping. It doesn't create or change anything.
5

Create your first ticket from an action item

Open any meeting at /dashboard/meetings that has extracted action items. (Don't have any? Upload a transcript via /dashboard/integrations/meet.)

Each action item card now has a Create Jira ticket button. Click it. Mnueron drafts a ticket with the action item text as the summary, the meeting URL and a transcript quote in the description, and the assignee email if one was extracted. Confirm or edit, then click Create. The ticket appears in your Jira within a second, and the meeting page now shows a status badge that updates when Jira state changes.

What we store

The encrypted API token plus your Atlassian email, Cloud URL, and chosen default project key. We never store the token in plain text; every decrypt writes a row to thesecret access log with the actor, route, and reason.

Per-user attribution

Tickets are attributed to the human who owns the token. If three people on a team want to create tickets from meetings, each connects their own Jira (one token, one user).

What can revoke access

Revoking the token in Atlassian instantly blocks Mnueron. You can also click Disconnect on the settings page; that drops the row immediately and any pending creates fail closed.

Free tier compatibility

Atlassian Cloud free tier supports the full REST API v3 surface Mnueron uses. No paid plan is required to get a working integration; upgrade only when you outgrow 10 users or 2GB of attachments.

Next reading