> 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/how-to-and-best-practices/managing-projects-and-time/sync-a-project-with-jira.md).

# Sync a project with Jira

If your team plans in Jira but tracks time in We360.ai, syncing keeps both sides in step: tasks, worklogs, and fields flow between a We360.ai project and its Jira counterpart.

{% hint style="warning" %}
The Jira integration is in **Alpha** and under active development. Behavior may change. Test on a non-critical project before rolling it out widely.
{% endhint %}

## 1. Connect Jira

Connect your Jira account from the Integrations settings, using either OAuth or an API token. For the full connection walkthrough, see [Integrations](https://docs.we360.ai/administration/settings-center/integrations).

## 2. Choose a sync direction

Decide how changes should travel:

* **Two-way**—changes on either side update the other.
* **Inbound only**—Jira updates We360.ai, but not the reverse.
* **Outbound only**—We360.ai updates Jira, but not the reverse.

Pick the direction that matches which tool is your team's source of truth.

## 3. Map projects and users

Link the Jira project to the We360.ai project it corresponds to, and map Jira users to their We360.ai accounts so work is attributed to the right people.

## 4. Map fields

Choose which fields stay in sync. Supported fields include summary, status, assignee, due date, comments, worklogs, and story points. Mapping worklogs is what keeps logged time consistent across both tools.

## 5. Enable real-time updates (optional)

Turn on the webhook option if you want Jira changes to appear in We360.ai immediately rather than on the next scheduled sync.

## 6. Verify the sync

Make a small change on one side and confirm it appears on the other in the direction you configured. Once verified, the project stays aligned as the team works.

{% hint style="info" %}
For how Jira sync fits into the module overall, see the [Projects & Tasks reference](https://docs.we360.ai/reference/work-and-time-management/product/work-and-time-management/projects-and-tasks).
{% endhint %}


---

# 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/how-to-and-best-practices/managing-projects-and-time/sync-a-project-with-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.