> For the complete documentation index, see [llms.txt](https://docs.we360.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.we360.ai/deployment-and-it-ops/integrations-and-api-access/integrations/portal-integrations/jira.md).

# Jira

Use this integration to sync **projects, tasks, and worklogs** between we360.ai and Jira, so your teams can keep working in Jira while their time and progress stay reflected in we360.ai.

Once connected, Jira issues appear as we360.ai tasks, time logged in we360.ai can be pushed back to Jira as worklogs, and issue changes flow into the task activity feed. Synced items show a **Jira badge** that links straight to the issue.

## Before you start

* You configure Jira in **Settings → Integrations**, on the **Jira** tile (Super Admin).
* Decide how you want to authenticate: **OAuth** (recommended) or an **API token**.
* Jira users are matched to we360.ai users **by email**, falling back to display name. Make sure your Jira users have a visible email that matches their we360.ai account.

## Connect Jira

{% tabs %}
{% tab title="OAuth (recommended)" %}
{% stepper %}
{% step %}

### Start the connection

On the Jira tile, click **Connect with Jira**.
{% endstep %}

{% step %}

### Authorize

Approve the request in the Jira authorization popup. No tokens are needed.
{% endstep %}

{% step %}

### Confirm

The tile shows **Connected via OAuth**. You can **Reconnect** at any time.
{% endstep %}
{% endstepper %}
{% endtab %}

{% tab title="API Token" %}
{% stepper %}
{% step %}

### Create a Jira API token

In your Atlassian account, create an API token for a service account.
{% endstep %}

{% step %}

### Enter the details

On the Jira tile, provide:

* **Jira Base URL** — e.g. `https://your-domain.atlassian.net`
* **Service Account Email**
* **API Token**
  {% endstep %}

{% step %}

### Test the connection

Click **Test Connection** to confirm the credentials work, then save.
{% endstep %}
{% endstepper %}
{% endtab %}
{% endtabs %}

## Configure the sync

After connecting, set how the two systems stay in step:

* **Sync Direction** — Bidirectional, Inbound only (Jira → we360.ai), or Outbound only (we360.ai → Jira).
* **Field toggles** — choose which fields sync each way. Inbound can include task creation, summary, description, status, assignee, story points, due date, comments, and attachments (up to 5 MB, off by default). Outbound can include summary, description, assignee, story points, due date, worklogs, comments, and attachments.
* **Story Points Field ID** — the Jira custom-field ID used for story points.
* **Unmapped users** — choose whether to skip, create a new user, or use a fallback user when a Jira user has no we360.ai match.
* **Auto-create projects on import** — off by default; when on, unmapped Jira projects create matching we360.ai projects.

{% hint style="info" %}
Use the **Jira Users** dialog and **Auto-Map to we360.ai Users** to line up accounts by email (then display name) before your first full sync.
{% endhint %}

## Map projects

Open **Project Mappings** on the tile to link a we360.ai project to a Jira project by its **project key**. You can also auto-import unmapped Jira projects to create new we360.ai projects, and view, enable, disable, or remove existing mappings. Mapping is at the **project level** (we360.ai project ↔ Jira project key).

## Keep it in sync

* **Scheduled sync** runs **daily** by default.
* **Trigger Sync** runs an on-demand sync.
* **Reset & Full Sync** re-imports everything without creating duplicates.
* **Webhook (near real-time)** — copy the URL from **Get Webhook URL** and add it in Jira under **Settings → Webhooks** to push inbound changes as they happen. Set a **Webhook Secret** on the tile to secure it.

## What syncs

* **Jira issues → we360.ai tasks:** summary, description, status, assignee, story points, due date, issue type, and reporter, with subtask hierarchy preserved.
* **Comments & attachments:** sync both ways (inbound attachments capped at 5 MB and off by default).
* **Issue history:** appears in the task **Activity** feed; changes made by unmapped Jira users are labelled **(via Jira)**.
* **Worklogs:** we360.ai time entries push to Jira as worklogs (outbound only). Status is inbound-only.

## Troubleshooting

#### The connection test fails

Recheck the Jira Base URL, service account email, and API token — or reconnect via OAuth.

#### Users are missing or unmatched

Confirm Jira users have a visible email matching their we360.ai account, then run **Auto-Map to we360.ai Users**. Review the **Recent Sync Errors** panel for details.

#### Changes aren't appearing quickly

The scheduled sync is daily — use **Trigger Sync** for an immediate run, or configure the webhook for near-real-time inbound updates.

## Support

* we360.ai integration support — `support@we360.ai`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.we360.ai/deployment-and-it-ops/integrations-and-api-access/integrations/portal-integrations/jira.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.