Possible data objects
Production scope is agreed per Jira setup before implementation.
- Projects and issues
- Users and mappings
- Worklogs and comments
- Status and references
Integration · Jira
Work in Jira. Billing and margin in ERP.
Development teams keep their working context. Neuronize transfers commercially relevant projects, time and assignments according to a defined data model.
The problem
Jira knows the work; ERP knows the contract, cost and invoice.
The integration connects both responsibilities without turning Jira into accounting or the ERP into a developer board.
Commercial context
Neuronize adds data Jira should not own for delivery work.
- Customer and contract
- Service and billing rate
- Internal cost
- Invoice and margin
Conflict and error rules
Duplicates, changes and missing assignments are handled explicitly.
- Leading system per field
- Idempotent transfer
- Error list and retry
- Traceable sync identifier
Example flow
Issue → worklog → review → invoice.
- 01
Issue
Task and project context start in Jira.
- 02
Worklog
Time is recorded with user and date.
- 03
Review
ERP assigns customer, service and billability.
- 04
Invoice
Approved time is billed.
FAQ
Jira integration questions
Is synchronisation bidirectional?
Direction is defined per object. Simple, explicit ownership is preferred; bidirectional sync only where necessary.
Can historical worklogs be imported?
Yes, when period, change behaviour and billing status are clearly scoped.
Is the Jira integration free?
Reusable standard parts may be included or funded through the extension programme. Setup-specific logic is assessed separately.
Related pages
Next step
Which Jira data should flow through billing?
We review projects, worklogs, users, conflicts and the intended billing path.