Last updated October 1, 2026
Section 2.6: Importing from Jira, Asana and Monday
New. If your projects live in Jira, Asana or Monday, you can pull them straight into ABRAM. An owner or admin connects the tool once for the whole organization. After that, anyone allowed to import picks projects from a list, previews them, and imports them with their structure and people.
Importing from these tools is included on every plan, Free included. ABRAM only reads from them. Nothing is written back to Jira, Asana or Monday.
1. What comes across
| In the tool | In ABRAM |
|---|---|
| Jira epic | Milestone |
| Jira issue | Deliverable |
| Jira sub-task | Checklist item on its deliverable |
| Asana section | Milestone |
| Asana task | Deliverable |
| Asana subtask | Checklist item on its deliverable |
| Monday group | Milestone |
| Monday item | Deliverable |
| Monday subitem | Checklist item on its deliverable |
Statuses, due dates and assignees come across too. People are matched to your team by email, the same way as a CSV import.
2. Connect the tool (owners and admins)
- Open Settings and go to Connectors under Integrations.
- Find Jira, Asana or Monday in the list.
- Click Connect Jira (or Connect Asana, Connect Monday) and sign in to the tool when asked.
Once connected, the row reads Connected by with your name, and shows an Import button.
The connection belongs to the organization. Members do not connect anything themselves. Before a tool is connected, members see Ask an admin to connect Jira. Asana and Monday stay out of members' view until an owner or admin connects them.
If a connection stops working, the row asks you to reconnect. Click Reconnect Jira (or the tool you use).
3. Import projects
You can start from either place:
- Projects in the sidebar, then the arrow next to New Project, then Import projects. In the sheet, choose Choose Jira projects (or Asana, Monday).
- Settings, Connectors, then Import on the connected tool's row.
Then:
- Pick the site or workspace. If the connected account sees more than one Jira site, or more than one Asana or Monday workspace, choose it first.
- Pick projects. Each project shows its item count and when it was last updated. Projects updated recently arrive ticked. A project over 1,000 items shows Over 1,000 items and cannot be ticked.
- Set the option. Sub-tasks as checklist items (Jira), Subtasks as checklist items (Asana) or Subitems as checklist items (Monday) is on by default.
- Click Preview. ABRAM reads each project and shows its progress, for example Read 200 of 640, then Ready.
4. Preview and import
The preview works the same as a CSV import. See Section 2.5 for the detail. In short:
- Choose a Client for each project, or Use me (in-house).
- Check the Statuses map. Labels ABRAM is unsure of carry Check.
- Check People. Anyone matched by email joins as draft crew when Add matched people as draft crew is on. For Jira, a person you matched in an earlier import arrives already picked and marked Last import. You can change it.
- A person who keeps their email private in the tool cannot be matched. Pick who they are, or their items import unassigned.
Click Import project (or Import 3 projects). Nobody is contacted. Send invites from the project's Team tab when you are ready.
On the summary, Undo import archives the projects this import created. Nothing is deleted.
5. Refresh a project from the source
After an import, you can pull the latest changes from the tool into the ABRAM project.
- Open the project.
- Open the More project actions menu, the three dots in the project header.
- Choose Refresh from Jira (or Asana, Monday).
- Click Refresh.
Changes made in the tool update the project. Items removed in the tool stay in ABRAM, and nobody is contacted. The result shows as a short message when the refresh finishes.
Refresh from appears for owners, admins and members who can import and manage that project.
6. Disconnect
On the tool's row in Connectors, click Disconnect, then Disconnect again to confirm. Nobody in the organization can import from that tool until an owner or admin connects it again. Projects already imported stay as they are.
Related guides
- Section 2.5: Importing Projects from a CSV File
- Section 1.6: Account Settings
- Section 3.4: Task Lists & Tracking
Agent reference: Jira, Asana and Monday import
- New in ABRAM 2.0.0. Included on every plan. Read only: ABRAM never writes to the source tool.
- One connection per organization, made by an owner or admin in Settings, Integrations, Connectors. Members import through that connection when they hold the Import projects access switch.
- Mapping: Jira epic, Asana section, Monday group become milestones; issues, tasks and items become deliverables; sub-tasks, subtasks and subitems become checklist items when the option is on.
- Limits: 1,000 items per project. Plan caps apply at write time.
- People are matched by email and land as draft crew; nobody is contacted. Jira remembers earlier matches as suggestions marked Last import.
- Refresh from (project actions menu) re-reads the source and updates the same project. Items removed at the source are kept.