Jira Cloud only
The integration supports Jira Cloud, connected through Atlassian.
note1 finds the Jira issue that already tracks an action item, or creates a new one. Create Jira tickets from meeting notes without retyping them.
Before creating anything, note1 searches the target's open issues and those closed in the last 30 days, and judges whether one already tracks the same work.
If an existing issue covers the action item, note1 links it and adds a comment with the meeting quote and a link to the meeting.
When a match is uncertain, note1 shows it as a suggestion in note1. You approve it with one click, or ignore it.
Action items with no match become new issues in Jira when auto-create is on, which is the default. With it off, they appear as "create" suggestions instead.
Choose Suggest, where matches wait for one-click approval in note1, or Auto-link, where strong matches link automatically and weaker ones become suggestions.
A new issue carries the context from the meeting, so the person doing the work does not need to replay the call.
The action item text becomes the issue title, and its description comes along.
The owner's name, the supporting quote and who said it.
A link back to the meeting in note1, with the full transcript and summary.
note1 sets the Jira assignee only when Jira exposes the person's email address.
About once an hour, note1 checks linked issues. When one is closed in Jira, note1 can show a "Possibly done" proposal on the action item, close the item automatically, or do nothing. Your team admin chooses which. Rejected proposals are not repeated.
A team admin opens Team, then Integrations, selects Jira and signs in through Atlassian. It is connected once for the whole team.
Choose the Jira project that receives new issues from meeting action items.
Pick Suggest, where matches wait for one-click approval, or Auto-link, where strong matches link automatically and weaker ones become suggestions.
The integration supports Jira Cloud, connected through Atlassian.
Your admin picks the Jira project that receives new issues.
note1 sets the assignee only when Jira exposes the person's email. Otherwise the issue is created without one.
Sync goes from note1 to Jira. Editing an action item in note1 after the issue exists does not update the issue, and closing it in note1 does not close the issue.
Items sync after each meeting is processed. Manually added items sync when you save them. You can retry a single item, or use Sync all on a meeting.
A team admin connects Jira Cloud once and picks a project. After each meeting, note1 creates a Jira issue for each action item that has no existing match. It sends action items, not the full meeting notes.
No. The integration supports Jira Cloud only.
Only when Jira exposes the person's email. When it does not, the issue is created without an assignee.
Before creating an issue, note1 searches the project's open issues and those closed in the last 30 days, and judges whether one tracks the same work. Matches are linked, with a comment, or suggested.
The action item text as the title, its description, the owner's name, the supporting quote with the speaker, and a link to the meeting in note1.
About once an hour, note1 checks linked issues. A closed issue becomes a "Possibly done" proposal, closes the action item automatically, or does nothing, depending on your admin's setting.
Other tools note1 sends action items to, and Slack. See every note1 integration on the integrations page.
Post meeting recaps and ask note1 from Slack.
Send action items to Linear, matched to existing issues.
Turn action items into GitHub issues without duplicates.
Send action items to Asana projects, matched to open tasks.
Add action items to a Trello list, matched to existing cards.
Send action items to a Todoist project as tasks.
Send action items to a Motion workspace as tasks.
Add action items to a Notion database as pages.
Connect Jira once for your team, pick where items go, and let note1 link or create issues after each meeting.