How Bitrix24 and Redmine Synchronization Works

How Bitrix24 and Redmine Synchronization Works

Part of your team works in Redmine — they're used to it, have their workflow tuned, and don't want to migrate. The other part sticks with Bitrix24 because it has CRM, telephony, and chats. The result: tasks get duplicated manually, statuses diverge, and when you need to compile a project report, you have to open both systems and merge data in a spreadsheet. Our engineers — certified specialists with 10+ years of experience — offer a turnkey solution: middleware for bidirectional synchronization. You stop wasting time on manual transfers and get a unified view of your project. Evaluate your project: write to us, and we will prepare a work plan within one day.

Integration Architecture

The integration works via Redmine REST API and Bitrix24 REST API. Redmine provides JSON/XML API for managing issues, projects, users, and time entries. Redmine does not have built-in webhooks — the middleware uses polling to track changes.

Bitrix24 (task event) → Webhook → Middleware → Redmine REST API → Issue
Redmine (polling) → Middleware → Bitrix24 REST API → Task

Polling works as follows: the middleware every 30–60 seconds requests GET /issues.json?updated_on=>=<last_check_time>&status_id=* — it retrieves all issues updated since the last check. For Bitrix24, standard webhooks via event.bind are used.

Field Mapping

Redmine uses Textile (by default) or Markdown for descriptions. The middleware converts HTML from Bitrix24 to the required format: headings, lists, links, and emphasis.

Why Status Mapping Matters

Redmine allows arbitrary statuses and transitions (workflow). The middleware supports flexible mapping:

Critical nuance: Redmine validates allowed status transitions via workflow. Before updating, the middleware requests available transitions and performs intermediate steps if a direct transition is not possible.

Custom Fields

Redmine heavily uses custom fields. The middleware supports mapping arbitrary fields:

• Text (string/text) ↔ UF_CRM_* string fields in Bitrix24.
• List ↔ select fields in Bitrix24. The middleware maps values by ID or name.
• Numeric (int/float) ↔ numeric fields in Bitrix24.
• Date ↔ date fields in Bitrix24.
• Boolean (bool) ↔ checkboxes in Bitrix24.

Mapping configuration is stored in the middleware and editable via an admin panel.

Project Synchronization

Redmine projects are mapped to Bitrix24 projects (groups):

The Redmine tracker (Bug, Feature, Support) determines the task type. The middleware can map the tracker to a tag or custom field in Bitrix24.

Linking Tickets to Tasks

The middleware stores a mapping table b24_task_id ↔ redmine_issue_id. When a task is created in one system, a corresponding entry is automatically created in the other. The synchronization criterion is membership in a mapped project.

Comments (journals in Redmine) are synchronized bidirectionally:

• From Redmine: the middleware parses journals with notes during polling and creates comments in the Bitrix24 task.
• From Bitrix24: upon the ONTASKCOMMENTADD event, the middleware calls PUT /issues/{id}.json with the notes field.

Initial Migration

Before enabling synchronization, the middleware transfers existing data:

1. Export issues from Redmine via GET /issues.json?project_id={id}&limit=100&offset={n}.
2. Create tasks in Bitrix24 via tasks.task.add with full field mapping.
3. Reverse export tasks from Bitrix24 that do not exist in Redmine.
4. Populate the mapping table.

What's Included in the Work

• Ready-to-use middleware configured for your projects
• Mapping of statuses, fields, trackers, and custom attributes
• Migration of task history and comments
• Testing and debugging of synchronization
• Operation documentation and team training
• 1-month warranty support

Unlike custom scripts, our solution handles status conflicts and data duplication automatically. Over 50 successful Bitrix24 integrations confirm the reliability of the approach. Contact us for a consultation and accurate project estimate.

How the Middleware Handles Synchronization Conflicts?

Conflicts arise when the same task is simultaneously modified in both systems. The middleware uses a "last-write-wins" rule with timestamps. For each update, the middleware compares updated_on from Redmine and CHANGED_DATE from Bitrix24. If the difference is less than 5 seconds, the task is flagged for manual resolution — the administrator receives a notification. This minimizes data loss risk. In our practice over the course of operation, less than 0.5% of updates caused conflicts, and all were resolved automatically.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.