Jira configuration

Every organization uses Jira in a slightly different way. That's why we let you configure your Jira settings in a way that supports your teams current practices.

Sync the relevant projects

First, confirm that all the necessary Jira Projects have been synced to Swarmia. These can be edited at any time by an admin. Once a project has been fully synced, a green check mark will appear.

Swarmia Jira settings

Map issue types and statuses

Within an organization, there are likely many issue types and issue statuses associated with them. Swarmia has tooling to help normalize that data. You can map your issue types to the four types available in Swarmia: epics, stories, tasks, and bugs. A common example is grouping bugs, incidents, and other similar issues into the Bugs bucket.

Like issue types, the use of issue statuses often varies between teams. When you connect Jira to Swarmia, we automatically map the issue statuses across your projects to the four Swarmia issue statuses: to do, in progress, done, and won't do. Organization admins can adjust the mappings at any time.

Status mapping

Map issues to teams

When you create a new team, Swarmia automatically suggests a project to be mapped to the team. If you have a setup where multiple teams use the same issue tracker project, you can assign the right issues to Swarmia teams based on, e.g., labels or custom fields. Assigning issue ownership for teams is an essential step, as only then will the Jira issues and related data be visible in Swramia.

Swarmia issues team settings

A project based team assignment