# Jira coexistence and transition (https://docs.akollo.com/en/connections/jira)



Your organisation can define how Akollo works alongside Jira, or let Akollo take responsibility for selected work-management activities.

## Capabilities [#capabilities]

| Area       | What it covers                     |
| ---------- | ---------------------------------- |
| Scope      | Selected project scope             |
| Work items | Work-item fields and relationships |
| People     | People and ownership               |
| Content    | Comments and attachments           |
| History    | Work logs and history              |
| Review     | Exceptions requiring review        |
| Acceptance | Transfer acceptance                |
| Changeover | Agreed changeover arrangements     |

Jira Cloud and Jira Data Center are both available as connectors. Jira Cloud asks for an email and API token, Jira Data Center for a personal access token. See [Connected systems](/en/connections) for the setup.

## Using this area [#using-this-area]

<Mermaid
  title="How a Jira transfer is accepted"
  chart="`flowchart LR
A[Agree which system handles each activity] --> B[Review coverage of agreed records]
B --> C{Open exceptions?}
C -->|Yes| D[Investigate and resolve]
D --> B
C -->|No| E[Accept the transfer]
E --> F[Agreed changeover]`"
/>

<Steps>
  <Step>
    ### Confirm which system to use [#confirm-which-system-to-use]

    Confirm which system to use for each activity, Jira or Akollo.
  </Step>

  <Step>
    ### Review coverage [#review-coverage]

    Before accepting a transfer, review coverage of the agreed records.
  </Step>

  <Step>
    ### Check the special cases [#check-the-special-cases]

    Custom fields, extensions, permissions and history need explicit coverage checks.
  </Step>

  <Step>
    ### Resolve exceptions [#resolve-exceptions]

    Investigate unresolved exceptions and resolve them before you accept the part of the transfer they belong to.
  </Step>

  <Step>
    ### Accept the transfer [#accept-the-transfer]

    Accept the transfer, then follow the agreed changeover arrangements.
  </Step>
</Steps>

<Callout type="warn" title="Warning">
  Do not accept a transfer while exceptions are unresolved. Custom fields, extensions, permissions and history are not covered unless you check them explicitly.
</Callout>

## Example [#example]

A project transfer includes tasks and attachments, but one custom field needs review. The project owner resolves the exception before accepting that part of the transfer.

## FAQ [#faq]

<Accordions type="single">
  <Accordion title="Do we have to move everything from Jira at once?">
    No. Your organisation chooses a selected project scope and decides which system handles each activity.
  </Accordion>

  <Accordion title="What needs extra checks before acceptance?">
    Custom fields, extensions, permissions and history need explicit coverage checks.
  </Accordion>

  <Accordion title="Who resolves an exception in a transfer?">
    In the example on this page, the project owner resolves the exception before accepting that part of the transfer.
  </Accordion>

  <Accordion title="Which Jira editions can be connected?">
    Jira Cloud, with an email and API token, and Jira Data Center, with a personal access token.
  </Accordion>
</Accordions>

## Related pages [#related-pages]

* [Connected systems](/en/connections)
* [Webhooks](/en/connections/webhooks)
* [Tasks and projects](/en/product-guide/tasks-and-projects)