Integration
In Bloomfilter, an integration represents the connection between Bloomfilter and external delivery systems where work is created and managed. Integrations enable Bloomfilter to continuously ingest delivery data such as projects, boards, tasks, statuses and activity; so it can be standardized, analyzed and visualized across the platform.
Business Value:
Integrations serves as the operational backbone of Bloomfilter; connecting external delivery systems, standardizing data across projects, boards, and workflows, and ensuring every downstream metric, dashboard, and strategic insight is built on accurate, consistently configured, and up-to-date delivery data.
DATA MANAGEMENT OVERVIEW
Bloomfilter’s Data Management module acts as the operational backbone of the platform. It controls how external systems are connected, how work is organized, and how delivery data is standardized before being used across dashboards, strategy views, and analytics.
By defining data sources, portfolios, projects, workflows, and board-level settings in one centralized location, Data Management ensures that all downstream insights are accurate, consistent, and scalable.
Why It’s Valuable:
Centralized Control: Manage all integrations, projects, and workflows from a single interface.
Reliable Analytics: Ensure metrics such as throughput, cycle time, and cost are calculated correctly.
Scalable Structure: Organize growing datasets into portfolios and projects with ease.
Data Freshness Visibility: Monitor integration health and sync status at a glance.
Reduced Configuration Risk: Prevent unmapped workflows or misconfigured boards from skewing results.
DATA SOURCES
The Data Sources section displays all connected external systems and the projects imported into Bloomfilter.
What It Shows:
Connected data platforms (e.g., Atlassian Jira Software Cloud)
Project key and name
Total boards per project
Integration owner
Last updated timestamp
Data freshness status
Activity trend visualization
Manual refresh action
PORTFOLIOS
The Portfolios section allows teams to group related projects together under a single portfolio, enabling higher-level visibility and organization across multiple workstreams. Portfolios act as a structural layer that connects projects to strategic and reporting views within Bloomfilter.
By organizing projects into portfolios, teams can better manage scale, align related initiatives, and simplify analysis across multiple projects and contributors.
Why It’s Valuable:
Portfolio-Level Visibility: View and manage multiple related projects in one place.
Strategic Organization: Group projects by product, initiative, or business objective.
Simplified Reporting: Enable roll-up insights across projects for leadership and stakeholders.
Ownership Clarity: Clearly identify portfolio owners and contributors.
Scalable Management: Easily add or remove projects as teams and initiatives evolve.
PROJECTS
The Projects section displays all individual projects imported from connected data sources. It provides a clear view of which projects are available in Bloomfilter and serves as the foundation for assigning projects to portfolios, workflows, and board settings.
Projects represent the core units of work ingestion and must be correctly configured to ensure accurate analytics and reporting across the platform.
Why It’s Valuable:
Project Visibility: View all available projects across connected data sources.
Configuration Foundation: Acts as the base layer for portfolio assignment and workflow mapping.
Controlled Onboarding: Select and manage which projects are actively used in Bloomfilter.
Data Accuracy: Ensure only relevant and properly configured projects contribute to analytics.
Scalable Setup: Easily accommodate new projects as teams expand.
WORKFLOWS
The Workflows section defines how status values from external systems are mapped into Bloomfilter’s standardized workflow stages. This mapping ensures that work moves through a consistent flow regardless of how statuses are named or structured in the source system.
Accurate workflow configuration is critical for calculating delivery metrics such as cycle time, throughput, and work in progress.
Why It’s Valuable:
Standardized Flow: Align different status schemes into a consistent workflow model.
Metric Accuracy: Ensure cycle time, throughput, and flow metrics are calculated correctly.
Cross-Team Consistency: Apply uniform workflow logic across multiple boards and projects.
Issue Detection: Identify unmapped or inactive statuses that could impact reporting.
Operational Confidence: Prevent workflow misalignment from skewing analytical results.
BOARD SETTINGS
The Board Settings section defines how Bloomfilter interprets board-level behaviors and working norms. These settings ensure that delivery metrics are calculated in alignment with how teams actually operate on their boards.
Board Settings allow teams to configure working hours, delivery methodology, and board-specific rules that directly influence analytical outcomes.
Why It’s Valuable:
Behavior Alignment: Align metrics with real team working patterns and schedules.
Methodology Support: Support different delivery methodologies such as Scrum or Kanban.
Metric Precision: Ensure velocity, throughput, and cycle-based metrics are interpreted correctly.
Board-Level Control: Apply tailored settings to individual boards without affecting others.
Analytical Consistency: Reduce discrepancies caused by board-specific configuration differences.
HOW TO ADD A NEW DATA SOURCE
This section outlines the process for connecting a new external system to Bloomfilter. Adding a data source allows Bloomfilter to ingest delivery data and make it available for configuration, analysis, and reporting across portfolios, projects, and workflows.
Once a data source is added, projects and boards can be mapped to workflows and organized into portfolios to ensure accurate and consistent analytics.
Steps:
Navigate to Data Management.
Select Data Sources.
Click Add New.
Choose the appropriate data source type.
Authenticate the external system.
Select the projects and boards to import.
Save the configuration.
HOW TO EDIT OR REFRESH AN EXISTING INTEGRATION
This section describes how to manage existing integrations and keep delivery data up to date. Users can manually refresh project data or adjust configurations without removing or re-adding the integration.
Regularly reviewing and refreshing integrations helps ensure that analytics, dashboards, and reports reflect the most current delivery activity.
Steps:
Navigate to Data Management.
Select Data Sources.
Locate the relevant project or board
Select Refresh to manually sync data.
Update related settings within Portfolios, Workflows, or Board Settings as needed.
Save changes.
Last updated