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
Choose how Swarmia syncs your Jira projects in issue tracker settings. Organization admins can update this at any time.
Sync all current and future projects syncs every Jira project automatically.
Select projects to sync syncs only the projects you choose.
Exclude projects from sync syncs all current and future projects except the projects you choose. Use this option to keep sensitive projects out of Swarmia without manually updating the list as new projects are created.
A green check mark appears when a project has finished syncing.
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.
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.
Last updated
Was this helpful?