Skip to main content

Jira connector

The Jira link lets you import the tickets of a Jira project into FoxPlan cards. Teams keep working in Jira; FoxPlan aggregates planning and steering.

It is configured in two distinct places, and that is the key to finding your way:

WhereWhat you do there
Settings → Workspace → JiraThe connection to the Jira server, once for the whole workspace
Project definition, Cards & Agility panelThe attachment of a Jira project and the status mapping, project by project

1. The connection (workspace)​

Settings → Workspace → Jira

Four fields, no more:

FieldContent
UrlThe Jira server address (e.g. https://your-org.atlassian.net)
IdentityThe technical account used to read the projects
Password / TokenThe account password or API token
Sprint internal fieldThe Jira custom field carrying the sprint, if you use agility

The Test button checks the link. On success, FoxPlan shows the list of available projects on that server — the most useful confirmation: it proves both that the connection works and that the account sees the expected projects. On failure, the message repeats the error returned by Jira.

There is no list of projects to synchronise here

This tab holds no project selection and no periodicity. The Jira project is chosen on each FoxPlan project, and the import is triggered manually.

2. The attachment (project)​

In the project definition, Cards & Agility panel:

  1. Tick Enable synchronisation.
  2. Click Refresh to fetch the Your Jira projects list.
  3. Select the Jira project to attach — it fills the project's Jira project field.
  4. Save the project: otherwise the selection is not kept for later imports.

Mapping statuses​

Below the selection, the kanban configuration table lets you associate, by drag and drop, a column of your kanban with a FoxPlan task status. That is where the correspondence between the Jira workflow and your columns is set — project by project, which allows different workflows from one project to the next.

3. Running the import​

Once the project is attached, a JIRA synchronisation button appears in the Planning toolbar of the project.

The import is manual and on demand: there is no automatic scheduling. At the end, FoxPlan shows "Import successful" followed by the number of items brought in.

Direction of the synchronisation

The operation imports from Jira into FoxPlan. It does not write back to Jira: tickets stay authoritative in their tool of origin.

Good practice​

  • Test the connection before attaching a project: the project list returned by the test tells you immediately whether the technical account has the right permissions.
  • Start with a single pilot project, until the column mapping is validated.
  • Only fill in the Sprint internal field if you use sprints: it is a custom field specific to each Jira instance.

See also​