Jira

Push tasks to Jira, pull them back, and keep client feedback flowing into the backlog your developers already work from.

Atarim team Updated 31 Jul 2026 · 7 min read

Integrations

Before you start

Relevant for

Project Managers, Frontend Developers and QA Engineers whose delivery work is planned in Jira.

Required knowledge

Familiarity with Jira projects, and enough access in Jira to authorise an app.

Tools & resources needed

An Atarim account on a plan that includes native integrations.
A Jira account with at least one project.
Permission to manage integrations in Atarim.

Client feedback captured visually in Atarim becomes an issue in the Jira project your developers already plan from. Setup has two parts — connect your Jira account, then decide which Atarim website feeds which Jira project. The destination is chosen per website, not once for the workspace.

Each Atarim website is mapped to a Jira project.

The Jira integration lets you push tasks to Jira, pull tasks back, and keep the two in sync. Client feedback captured visually in Atarim becomes an issue in the project your developers already plan from, with the task’s details carried across.

Setup has two parts: connect your Jira account, then decide which Atarim website feeds which Jira project.

Connect Jira

In Atarim, go to Settings.

Under Connected Apps, select Integrations.

Find Jira. Before it is connected, the panel explains that you need to connect your Jira account first and to use the button to proceed.

Select the connect button. Atlassian opens a page headed Atarim is requesting access to your Atlassian account.

Check the site shown under Use app on is the Jira site you mean.

Review the access being requested, then select Accept. You are returned to Atarim, and a green banner confirms Jira is connected with a Manage Connection button beside it.

The Jira row in Atarim's Integrations panel before connecting — Find Jira in Settings → Connected Apps → Integrations

The Atlassian access request page showing the site under Use app on and the Accept button — Check the site under Use app on, review the access, then select Accept

Note

The consent screen lists what Atarim needs in Jira — manage jira-webhook, and view and update jira-work. Accepting grants access to your data in all places you can access where the app is installed, and agrees to Atarim’s privacy policy and terms of use.

Check the site before accepting

If your organisation has more than one Atlassian site, the one named under Use app on is the one being connected. Accepting on the wrong site connects the wrong Jira, and you will only discover it when the project list looks unfamiliar.

Jira is a plan feature

Where your plan does not include native integrations the option is locked and names the minimum plan required, and only the workspace owner can change the subscription. If Integrations is not in your sidebar at all, your role does not have access to it. Once connected, the panel offers a reconnect option — use it if the connection stops working after changes on the Jira side, rather than removing and re-adding the integration. Learn More About User Roles And Permissions

Choose the Website and Project

Configuration happens in two saves, which is easy to miss because they look similar. First you pick the website, then you pick the Jira project it feeds.

1. Select the Website

Under Websites, open the dropdown showing Select a website.

Choose the Atarim website you want to connect.

Select Save Project. The website is stored as the one this configuration applies to.

The Websites dropdown and Save Project button in Atarim's Jira configuration — Choose the website, then Save Project — this stores the website, not the Jira project

2. Turn On Syncing and Pick the Jira Project

Switch on the option to automatically push and sync tasks created on your Atarim dashboard to Jira.

Under Project, open the dropdown showing Select a project and choose the Jira project.

Select Save. Tasks from that website now push to the chosen Jira project.

Repeat for each website you want connected.

The sync switch and Project dropdown in Atarim's Jira configuration, with the Save button — Switch on syncing, choose the Jira project, then Save — the second save is the one that stores it

Both saves are needed

Save Project and Save do different jobs despite sitting a few lines apart. Selecting a website and stopping there leaves nothing syncing, because no Jira project has been chosen yet.

What Gets Pushed

Each task pushed to Jira carries its name, a link back to the task, its status, its urgency and its comments. After the initial push, changes made on the Atarim dashboard continue to sync across to Jira.

The same Atarim task appearing as an issue in a Jira project — …arriving as an issue in the mapped Jira project

A Jira issue showing the Atarim task details carried across — The issue carries the name, link, status, urgency and comments

An empty project list means Jira is not reachable

The Save button is disabled while no projects are available. If the list stays empty after connecting, Atarim could not retrieve your projects — use Manage Connection to reconnect rather than waiting.

Recommendation

Map to a project your team actually grooms, not a catch-all. Because syncing runs continuously once configured, client feedback arrives without pause — and a project nobody looks at becomes a backlog of unread issues rather than work getting done.

Using Jira in a Workflow

The per-website mapping above pushes everything from that website automatically. If you would rather be selective, Jira is also available as an action inside Workflows — so you can send only the tasks that meet conditions you set.

Create or edit a workflow.

Add the Jira action, listed under Integrations.

Choose the Project the task should be created in. A Jira project is required — the workflow will not validate without one.

Save the workflow.

Jira is available as a workflow action for selective pushing

Use one route or the other, not both

Use a workflow when only some tasks belong in Jira — bugs but not content requests, say, or only work above a certain priority. Use the per-website mapping when everything from that site should go across. Doing both for the same website will produce duplicate issues.

Note

The workflow action needs the Jira integration connected first. Connect the account before building the workflow, or the project list will have nothing to offer. Explore Workflow (Automation)

Setup at a Glance

Step	Where it happens	What it needs
Switch Jira on	Atarim → Integrations	A plan that includes it, and permission to manage integrations.
Accept the access request	Atlassian	The right Atlassian site under Use app on.
Select the website	Atarim	A website in your workspace.
Save Project	Atarim	A website selected.
Turn on automatic syncing	Atarim	The website saved.
Select the Jira project	Atarim	A live connection, so projects can load.
Save	Atarim	A project selected.
Repeat per website	Atarim	Each website configured separately.

Benefits

Benefit	In practice
Feedback reaches the backlog	Client requests arrive where development work is actually planned.
Sync works both ways	Tasks can move from Atarim to Jira and back.
Per-website mapping	Different clients can feed different Jira projects from one workspace.
Context travels with the task	Issues arrive with the task’s details rather than a bare title.
Clients stay in Atarim	They never need a Jira seat for their feedback to be tracked.

Example Use Cases

Situation	How to set it up
Developers plan sprints in Jira	Map the client’s website to the delivery project so requests enter the backlog automatically.
Several clients, several Jira projects	Map each website to its own project.
Clients giving visual feedback	Let them work in Atarim while issues appear in Jira.
Separating client work from internal work	Point the mapping at a dedicated project rather than a shared one.
Reporting from Jira	Sync feedback in so client requests appear in existing reports.

FAQs

Does sync work in both directions?

Yes. Tasks can be pushed to Jira, pulled back, and kept in sync.

Can different websites use different Jira projects?

Yes — that is how the mapping works. Each website is configured separately.

Do I need to create the Jira project first?

Yes. Atarim can only choose from projects that already exist in your connected Jira account.

What does Atarim push to Jira?

The task name, a link back to it, its status, urgency and comments. Later dashboard changes continue syncing across.

Why is the Save button greyed out?

Because no Jira projects have loaded. That usually means the connection is not returning data — reconnect and try again.

Do clients need a Jira account?

No. Clients work in Atarim; syncing happens between your two accounts.

Can I send only some tasks to Jira?

Yes. Use the Jira action inside a workflow instead of the per-website mapping, so only tasks meeting your conditions are pushed.

Can I change the mapping later?

Yes. Choose a different project for that website and select Save again.

What if the connection breaks?

Use the reconnect option in the Jira row of the Integrations panel.

Common issues

The Project list is empty and Save is disabled — Atarim cannot retrieve your Jira projects. Reconnect the integration.
The Jira option is locked — your plan does not include native integrations. The lock names the minimum plan required.
Integrations is not in your settings sidebar — your role does not have access. Ask an Administrator.
Your project is not in the list — create it in Jira first, then reconnect so the list refreshes.
Tasks are not reaching Jira — confirm you used both saves (Save Project for the website and Save for the Jira project) and that automatic syncing is switched on.
Tasks landed in the wrong project — the mapping points elsewhere. Change it and save again.
Issues are being created twice — the website is mapped and a workflow is pushing to Jira. Use one or the other.
The workflow will not save — a Jira project is required on the action. Choose one before saving.
Only some websites sync — each website is mapped separately. Check the ones that are not syncing have a project set.
The wrong Jira site got connected — the site under Use app on was the wrong one. Use Manage Connection to reconnect and accept on the right site.
You cannot authorise Atarim in Jira — your Jira account may not have permission to approve apps. Ask a Jira admin.

Conclusion

Jira setup is short but has one detail that catches people out: the destination is chosen per website, not once for the workspace. Connect the account, then map each website to the Jira project it should feed.

Point the mapping at a project your team genuinely grooms — syncing runs continuously once configured, and an unwatched project quietly fills up.

Tips & best practices

Create the Jira project before you start, so it is selectable during setup.
Map each website deliberately rather than pointing everything at one project.
Use a project your team actively grooms.
Use both saves — Save Project for the website, then Save for the project.
Reconnect rather than reinstall if projects stop loading.
Choose either the per-website mapping or a workflow for a given site, not both.
Check each website’s mapping when adding a new client.

Was this article helpful?

The Stack: Mapping Your Preferred Plugin to Each Functional Category What It’s For, and Why It’s Worth Filling In Atarim’s workflows and AI agents constantly need to answer one question: which tool does this job Integrations · 13 min read Atarim MCP: Connecting Claude, Codex, and Other Coding Agents Step-by-Step Guide What This Actually Does Think of it as a direct line between Atarim and your developer’s AI assistant. Normally, if a client Integrations · 13 min read Atarim Figma Plugin: Overview & Why It Exists Select a frame, pick a destination, push. Feedback happens in Atarim afterwards. The Atarim Figma Plugin pushes design frames from Figma into Atarim, where Integrations · 9 min read