LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Multiple Jira organizations
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configuration and data quality
    • Teams & members
      • Creating & managing teams
        • Teams API
      • Contributors
      • Roles and permissions
      • Inviting team members
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • Pull request exclusions
    • Linking pull requests to issues
    • Investment categories
    • Deployments
      • Generate deployments from merged pull requests
      • Generate deployments from GitHub deployments
      • Generate deployments from GitHub checks
      • Generate deployments via the API
        • Generate deployments for monorepos via the API
    • Sprint configuration
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Focus summary
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Continuous improvement
    • Working agreements
  • Notifications
    • Team notifications
    • Personal notifications
  • Retrospectives with Swarmia
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Sprints
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • Organization settings
  • Team settings

Was this helpful?

Configuration and data quality

The article provides an overview of settings to ensure your data is accurate in Swarmia and links you to further reading and the related settings in the Swramia app.

PreviousOther source code hosting integrationsNextTeams & members

Last updated 7 days ago

Was this helpful?

Data quality is crucial for building trust in engineering intelligence tools and ensuring sound decision-making. Teams often work differently—using Scrum, Kanban, or other practices—which can lead to inconsistencies. Issues like mismatched user identities, inconsistent issue tracking, or conflicting label usage can impact data reliability. That’s why we prioritize accurate and transparent data by showing what's behind each metric, automating the setup whenever possible, and offering tools to close any quality gaps that might remain.

Organization settings

At the Swarmia organization level, you integrate your tools, configure global settings, and organize your contributors into Swarmia teams. At the team level, you ensure the right issues and pull requests are assigned to teams.

  • . To see your data in Swarmia, you need to organize contributors into teams. You can sync teams from GitHub, use Swarmia API, or create teams manually. .

  • . Ensure work items are assigned to the right people. Swarmia automatically merges the identities across the systems contributors interact with. Make manual adjustments as needed.

  • . Select projects to sync. Swarmia maps issue types and statuses automatically and you can make adjustments if needed. .

  • . By default, pull requests from all synced repositories are visible in the Swarmia metrics. Create filters to exclude specific pull requests automatically. .

  • . Use Swarmia default settings or define rules on how to group pull requests and issues into investment categories. .

  • . Configure deployments to track DORA metrics. Swarmia supports multiple setup options to match your needs. .

Team settings

Once the organization-level settings are ready, you and the teams can proceed with team-level settings to ensure the right issues and pull requests are assigned to each team.

  • . Assign issues to teams to make them visible in Swarmia. Swarmia automatically suggests a project for each team. If multiple teams use the same project, you can assign the issues with, e.g., labels or custom fields. .

  • . By default, Swarmia associates everyone's pull requests with all the teams they belong to. You can create rules to exclude specific pull requests from your team. .

  • Slack notifications make work visible and provide a feedback loop to stick to working agreements to create lasting habits. .

  • . Invite team members to collaborate in Swarmia and enable their personal GitHub-Slack notifications.

  • . Swarmia automatically links pull requests to issues and offers ways to do it manually when a PR contains too little information to automatically link. .

  • . A high categorization rate (more than 80% of work categorized) is essential to have good visibility into where engineering time goes. You can find the items the categorization rules didn't catch and assign the right category in the .

  • . Swarmia automatically selects a Jira board that has Sprints and enables sprint activity tracking. You can change the board in .

Creating teams
Teams & members settings
Contributors
Contributor settings.
Issues: projects, types, statuses
Swarmia Jira settings
Pull request settings
Investment categories
Investment category settings
Deployments
Deployments settings
Team issue settings
Team pull request settings
Team notifications.
Team notifications settings
Inviting team members
Swarmia home.
Linking pull requests to issues
Pull request inbox
Investment balance
Configuring sprints
Team issue settings
Pull request exclusions
Pull request exclusions
Improving categorization rate
Mapping issues to teams