> ## Documentation Index
> Fetch the complete documentation index at: https://help.gowindmill.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira

> Connect Jira to Windmill to bring issues, sprints, and engineering progress into recaps, 1:1 prep, and performance reviews with proper per-person attribution.

## Benefits of connecting Jira to Windmill

Connecting Jira to Windmill ensures engineering work is accurately reflected in 1:1s and performance reviews — without engineers needing to write self-promotional summaries or dig through old tickets.

* Captures real progress, ownership, and work patterns automatically
* Reduces review prep time for engineers and managers
* Highlights meaningful contributions beyond lines of code (debugging, triage, architecture, support)
* Brings visibility to collaboration, problem-solving, and delivery reliability
* Makes performance reviews more fair, objective, and grounded in actual work

Windmill turns ongoing Jira activity into structured performance and coaching context.

## Connected data

When Jira is connected, Windmill securely reads **work activity metadata**, not code:

| Data Type                                         | How Windmill Uses It                                           |
| ------------------------------------------------- | -------------------------------------------------------------- |
| Issues created, owned, or completed               | Shows ownership, execution, and delivery follow-through        |
| Status changes (e.g., To Do → In Progress → Done) | Highlights workflow efficiency and predictability              |
| Sprint membership + velocity signals              | Helps contextualize workload and throughput over time          |
| Comments, collaboration, and handoffs             | Surfaces teamwork, communication, and problem-solving patterns |
| Story points, tags, and issue types               | Helps differentiate project work vs. bugs vs. support load     |

> Windmill does **not** ingest full ticket bodies unless explicitly enabled — only the context needed for performance insight.

## Permissions

Windmill requests **read-only**, scoped access to selected projects via Jira’s API. Windmill will have access to only the boards in Jira that the person who connected Jira has access to. This means that if you are missing data from Jira in Windmill, it is likely the person who authed Jira did not have access to that data.

| Permission                                        | Purpose                                                      |
| ------------------------------------------------- | ------------------------------------------------------------ |
| Read issues + status metadata                     | To reflect progress and ownership in performance discussions |
| Read comments + collaboration metadata            | To show teamwork and communication patterns                  |
| Read project + sprint association                 | To understand workload and project context                   |
| **No write access**                               | Windmill never modifies issues, comments, or workflow states |
| **Scoped access only to selected teams/projects** | You choose exactly what is included in sync                  |

> Windmill follows least-privilege access and only ingests metadata relevant to coaching and performance — not sensitive or unnecessary detail.

## Username mapping

Jira uses specific usernames that don't always map to employee email addresses. If you see Jira activities that aren't associated with a team member or are associated with the wrong team member, Windmill Admins can fix this.

To update username mapping:

1. Go to **Settings** in Windmill
2. Select the **Integrations** tab
3. Select **Jira**
4. Select the **Mapping** tab to see all usernames and their current mappings
5. Click **Update mapping** to edit assignments

## FAQs

<AccordionGroup>
  <Accordion title="Does Windmill change or update Jira tickets?">
    No. The integration is strictly read-only.
  </Accordion>

  <Accordion title="Do we need to sync our entire Jira workspace?">
    No. You choose which projects or teams to sync. You can update or revoke access at any time.
  </Accordion>

  <Accordion title="Does Windmill store ticket content?">
    By default, no — Windmill stores metadata and summaries, not full ticket descriptions. Full content can be enabled only if explicitly approved.
  </Accordion>

  <Accordion title="How often does Windmill sync Jira data?">
    Continuously. Changes appear in Windmill shortly after they happen in Jira.
  </Accordion>

  <Accordion title="Is the integration secure?">
    Yes. Windmill uses encrypted data transfer, secure storage, scoped OAuth access, and meets SOC 2 compliance standards.
  </Accordion>

  <Accordion title="What happens if an engineer leaves or changes teams?">
    Their historical contributions remain available for context, but Windmill stops associating new activity once they are deactivated.
  </Accordion>
</AccordionGroup>